JScript. Dynamic languages’ forgotten cousin.
Update 27 July 2007: Looks like there’s resurgent interest in serious Javascript use on the server-side.
In response to Han’s Nowak’s question of what new language to use, and since Python had to be excluded, may I suggest JScript.NET?
(I’ve moved most of the technical aspects of the discussion over to the Python, Zope and dotNET blog. )
The question I’d like to pose here, is why a sloppy (in the good sense) language like JScript doesn’t gain more traction among the development community?
I’m keen to hear what your thoughts are.
March 15th, 2005 at 11:32 pm
One answer Packages. Languages that excel allow programmers to use the work of others. Take C and python.. the #include and the import statement are the corner of their success. Now what was that statement in JScript?? Oh I can’t remember..
May 11th, 2005 at 11:45 am
Though not entirely current anymore, I can’t help but respond.
import System
import System.Windows.Forms
import System.IO
All valid JScript.NET imports.
Anthony, have you even LOOKED at JScript.NET? JScript.NET uses all of the .NET assemblies, any COM object you like, dynamically eval other JScript code (in some cases) and otherwise generally participate in .NET in *exactly the same ways* as C#. JScript.NET is compiled, just like C. It can be used to build DLL assemblies which in turn can be used in the languages like Python and C via COM wrappers.
Exactly which “Packages” can’t JScript.NET handle.
March 11th, 2006 at 9:32 pm
[...] Luckily for JavaScript, implementations such as Rhino and JScript leverage off the OO libraries of JVM and CLR respectively. I think these implementations have great potential, since they benefit from the OO libraries (objects whose behaviour are easier to figure out), but offer the advantage of prototypes, where behavior can be modified without having to subclass. [...]