In the discussion further above, we agreed (I thought), that the serverside part
of a Web-Application becomes (much) more light these days
This is one hell of a long thread now so while i cant remember the post but i do agree.

So, "comfort whilst developing things in a serverside language" is not that
critical anymore.
I disagree, when i develop web apps the whole stack of technology i am using matters to me

So, a Web-App is not being developed as a "sequence of linked pages" so much anymore,
but mostly coming as a Single-Page-App, which refreshes parts of its "panel-areas"
dynamically, with new (per ajax requested) "View- and Model-Blobs and -Templates".
Modal and non-modal Popup-Dialogues, Grids, Trees, and the whole bunch of other
"templatable Controls" - everything's there and handled dynamically at the
clientside, often not needing a roundtrip over the server,
So, modern WebApps define themselves over the clientside js-Framework one decides to saddle-on,
and much less over what environment or language might be used at the server-end,
to "massage the JSON" in the incoming ajax-requests.
I have paraphrased you above just to make what you were saying clearer Olaf, as while you obviously have lost of knowledge you do sometimes go into more detail then i think is needed imho

Again i don't disagree with what your saying here but regardless of that for me Classic ASP is a different product to VB6 and an Inferior one.

VB6 does what it does well, or at least it can do if in the right hands

Classic ASP was designed when the Web was a different place and imho as a tool is far outstripped by ASP.Net and many other web languages like PHP, ColdFusion, Python, even for the backend stuff of web apps.

VB Script is just not great to use in the Web and if you are just going to solely use JavaScript then why use it at all?

I Personally use a mix of ASP.Net ( c#), JavaScript, JQuery and Json, HTML5 and CSS3 for my web apps and as a technology set they all work really nicely together