Content deleted Content added
Northgrove (talk | contribs) JScript .NET as a natural successor to JScript |
Northgrove (talk | contribs) |
||
Line 46:
The article is started with this claim, and I was always confused by it since JScript .NET isn't even a normal scripting language per se, but a compiled language. We use JScript (i.e. JavaScript with MS extensions) prominently in some of our applications, but could never switch to JScript .NET since it's not a matter of modifying text files on the fly, which is the whole point of why we didn't just make it called compiled C++ code in the first place.
My point is that I personally don't see JScript .NET as a successor due to it striving for a bit different goal (running as a server-side application, and not on the client as a script), and I believe this is also a reason to why it hasn't taken of well.
I'm not sure it's a successor, much less natural. -- [[User:Northgrove|Northgrove]] 08:38, 9 August 2006 (UTC) | |||