Article:		VBScript or Perl?
Subject:		Why not JScript?
Date:		2003-11-18 22:24:04
From:		anonymous2
It's also pre-installed. It supports prototype based OO. Lots of people are already familiar with Javascript by using it in the web page setting. And it's neither wordy like VBScript, nor cryptic as Perl.

Showing messages 1 through 3 of 3.

• Why not JScript?
  2003-11-23 07:29:16  anonymous2 [Reply | View]
  
  
  In a WSH environment JScript support is limitted. Prototype-based inheritance just doesn't work, so this renders JScript useless. I haven't worked with WSH extensive, so I might be wrong.

• Why not JScript?
  2003-11-19 20:12:00  Robbie Allen | [Reply | View]
  
  
  I think one could make a very good argument for JScript. Especially with the integration into the .NET Framework, it is an attractive option. I'm not sure why it hasn't picked up as big of a following (from what I've seen) for doing sys admin scripting as VBScript.
  
  I've done a lot with Javascript in HTML, but not in the WSH environment. One thing I may do to write companion JScript examples for all of the code in the AD Cookbook: http://www.rallenhome.com/books/adcookbook/code.html. Then I can look at the web logs and see what is the most popular.

• Python
  2003-11-19 05:00:18  anonymous2 [Reply | View]
  
  
  Python fits very well in the windows world (can talk to dll's, COM, etc) and has cleaner object orientation than perl. Python stresses clarity and simplicity, yet it is also a very powerful language.