I'd agree, something is needed - but it should be C# based, not VB to prevent people assuming it's anything like the awfulness that was VBA. And it needs to be designed from the ground up to be safe and secure ... so it'll never happen.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
Nothing against going to C#, and you have good justification. And yes it needs to have the security issues fix such that there are different levels, and the code is checked to make sure that it does not exceed whatever level is chosen.
So - consider you have a language who's primary (and by far, dominant) usage is to render text (as in web-pages) - then the 'suck-it-up' can be exchanged for the convenient in accomplishing the task.
With the above considerations in mind, if I fault them anything, it is that they are so similar, often on the same pages (initially) and that took extra getting-used-to. They're heavily used because, like it or not, they're the right tool for the job.
* object types, in either, language are the obvious exceptions
Ignoring the sarcasm, that would of course be yet another argument for not touching that stuff until the worst junk has been weeded out. Unfortunately that has not happened yet. They still get even crazier and seem to think that it has to be such a miserable experience, otherwise it's not real web programming.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
the entire f***ing web stack falls into the last category.
I really do understand that. Especially for those of us who started out as desktop devs.
There were so many years of becoming strongly involved with desktop before web was much of a thing at all.
I'm guessing that you were a desktop dev before the web really took off. And that means even if you started around 2000. Now the whole thing is all web centric.
Anyways, I agree with your sentiment whole-heartedly.
However, I am truly amazed with the new ASP.NET Core stuff. It feels like one solid framework / dev environment which you add things as you need them.
I wrote an article on it here at CP[^] (and that's not why I'm writing this) and I think Microsoft has a solid deal there if they can continue to support it. It's more elegant than any of the other full-stack solutions out there -- IMHO.
0. I will work not work with Ruby or other duck-typed, runtime-typed, or "script kiddie" languages;
8. I will not waste my valuable time learning some half-ass open source latest rage just because every other idiot says it's the latest rage;
I also quoted it in my bio, just to drive the point home.
Bonus point (not languages but methodologies):
7. I will write code using my own well thought out architecture, not some fly-by-the-seat-of-your-pants Agile methodology bullsh*t;
Yes, definitely . You're one of the people in this forum I keep in the highest esteem. Solid logic, facts and pragmatism... much better than the marketers' paradise programming has become in the last decades.