It's funny, but I also started out using JScript for my ASP pages. The only thing that was alien was dealing with COM Enumerables (Active Record results, etc). I was also into the Alt.Net space pretty early on. I used Castle Monorail (iirc that was the name) for a few things, and was genuinely happy to see ASP.Net MVC come from MS as a prescribed solution.
Of course, I would often bypass certain behavior as I didn't like the way some parts work, specifically I'd override the user/token behavior, allowing me to both stow a few more things in the encrypted token, as well as be able to use ARR to relay to other things (node, java) using the same user cookie (encrypted token).
The following is in response to a comment directly on TFA regarding the "mess" that was WebForms... What it really came out of was the pain in the shear number of differences in JS between the browsers at the time... in 1997-2000 there were radical changes. People complain today about the missing pieces in JS between browsers/engines, but it's NOTHING like the pain of dramatically different DOM implementations... Layer/Frame NN/IE... and if you had to support Netscape 4.x when IE5-6 were just released, OMG that was a nightmare.
I'm a big fan of JS, and love what it's become today (fatigue from webpack, babel, etc and all), but at that point in time, it was truly painful. IE6 getting well over 90% market share was a bit of a mixed blessing as all the old cruft of the v4 browsers had passed, and the newer DOM started to take hold with Mozilla and IE. JQuery wasn't around until 2006, and prototype (the library) had quite a few issues itself.
People were begging for a server-side solution to all the client-side problems. That's how we got WebForms, and frankly by the time ASP.Net MVC came out the landscape had changed dramatically for the better.
I think a lot of developers today either don't remember, or came in after the pain of client side development in the mid-late 90's. It really wasn't the JS language (though prior to nn4/ie4 it was kind of bad). People didn't update their browsers, and corporate standards held things far longer. I was working in a job that required Netscape Navigator 4.08 support when IE6 was released, and IIRC NN8 was in beta. I had to do some interactive charting and stack diagrams and had to support both newer and older interfaces. To say it was painful would be an understatement. I'll take what we have today with the node/npm space every time over what it was like prior to 2003. Although we've now had jQuery over a decade, and node/npm for over 6-8 years, there were some bad old days before.
Of course, I would often bypass certain behavior as I didn't like the way some parts work, specifically I'd override the user/token behavior, allowing me to both stow a few more things in the encrypted token, as well as be able to use ARR to relay to other things (node, java) using the same user cookie (encrypted token).
The following is in response to a comment directly on TFA regarding the "mess" that was WebForms... What it really came out of was the pain in the shear number of differences in JS between the browsers at the time... in 1997-2000 there were radical changes. People complain today about the missing pieces in JS between browsers/engines, but it's NOTHING like the pain of dramatically different DOM implementations... Layer/Frame NN/IE... and if you had to support Netscape 4.x when IE5-6 were just released, OMG that was a nightmare.
I'm a big fan of JS, and love what it's become today (fatigue from webpack, babel, etc and all), but at that point in time, it was truly painful. IE6 getting well over 90% market share was a bit of a mixed blessing as all the old cruft of the v4 browsers had passed, and the newer DOM started to take hold with Mozilla and IE. JQuery wasn't around until 2006, and prototype (the library) had quite a few issues itself.
People were begging for a server-side solution to all the client-side problems. That's how we got WebForms, and frankly by the time ASP.Net MVC came out the landscape had changed dramatically for the better.
I think a lot of developers today either don't remember, or came in after the pain of client side development in the mid-late 90's. It really wasn't the JS language (though prior to nn4/ie4 it was kind of bad). People didn't update their browsers, and corporate standards held things far longer. I was working in a job that required Netscape Navigator 4.08 support when IE6 was released, and IIRC NN8 was in beta. I had to do some interactive charting and stack diagrams and had to support both newer and older interfaces. To say it was painful would be an understatement. I'll take what we have today with the node/npm space every time over what it was like prior to 2003. Although we've now had jQuery over a decade, and node/npm for over 6-8 years, there were some bad old days before.