Content deleted Content added
No edit summary |
m Added some information about "JScript .NET as a natural successor to JScript" |
||
Line 49:
I'm not sure it's a successor, much less natural. -- [[User:Northgrove|Northgrove]] 08:38, 9 August 2006 (UTC)
The claim is half valid.
To the best of my knowledge, JScript .NET was indeed designed as a successor to JScript for server-side Web applications. This means in scenarios of migrating ASP (Active Server Pages) + JScript code to ASP.NET + JScript .NET code.
However, while both are based on ECMAScript (3<sup>rd</sup> Edition for original JScript and Pre-4<sup>th</sup> edition for JScript .NET), the fact that JScript .NET is much more typed, less dynamic, and compiled to the same MSIL as C# or J# makes it very different to work with in the end.
The need for more dynamic languages in .NET have been acknowledged and the DLR (Dynamic Language Runtime) is designed to allow languages closer to the original JScript and Python. Another implementation of JScript, called Managed JScript, is based on the DLR, and is much closer to the original JScript than JScript .NET could ever be. It supports being hosted in other applications and parsing while executing, while JScript .NET required the whole script to be available and parsed before starting the execution.
[[User:PhMajerus|PhMajerus]]
== Javascript and ECMAScript ==
| |||