> I am looking for a good scripting engine for the MS Windows platform.
>> I am looking for a good scripting engine for the MS Windows platform.
>
[quoted text clipped - 4 lines]
> If you want some simple batching, then using .BAT files may be enough
> (built-in Windows)
Somewhere between batch files and perl/python/ruby/bash is WSH, Windows
Scripting Host. WSH is actually a platform, and languages you can write in
include VBScript, JavaScript, and a couple others I don't recall off the top
of my head.
> If you need something a little more complicated than batching, look
> into a scripting language. Some examples: Perl, Python, Ruby, BASH.
>
> If you are doing anything more complicated than that, Java might be
> the right choice for you. You can download the development kit from
> Sun, for no charge.
- Oliver
Andy Dingley - 13 Feb 2007 13:01 GMT
>Somewhere between batch files and perl/python/ruby/bash is WSH,
> Windows Scripting Host.
That's evil! Why don't you just recommend he surfs a few pr0n sites
with "Install and run anything" turned on?
WSH is _horribly_ insecure. Avoid it like the plague. it exists to
fill a niche in M$oft's world view (How do we make the ASP languages
run from the command line?) rather than because it's a good or
trustworthy platform.
If you want a "scripting language" for Windows, then I'd strongly
recommend Python. Perl works too, as does Ruby. Python and Ruby are
also better languages than JScript or VBScript.
You might even install Cygwin (good) and then learn Unix shell
scripting (usually pretty obsolete, although still worth knowing
about).
Java is _not_ a scripting language by any means. Groovy is only a
useful scripting language if you're already in a JVM-friendly
environment, which you're probably not.
Oliver Wong - 13 Feb 2007 15:46 GMT
>>Somewhere between batch files and perl/python/ruby/bash is WSH,
>> Windows Scripting Host.
[quoted text clipped - 14 lines]
> scripting (usually pretty obsolete, although still worth knowing
> about).
Out of curiosity, what vulnerabilities does writing your scripts in WSH
open you up to that writing your scripts in Python/Perl/Ruby/Bash/whatever
does not?
- Oliver
Andy Dingley - 13 Feb 2007 16:56 GMT
> Out of curiosity, what vulnerabilities does writing your scripts in WSH
> open you up to that writing your scripts in
> Python/Perl/Ruby/Bash/whatever does not?
Ones based on exploits via ActiveX. WSH doesn't even have IE's level
of protection here.
The problem isn't with the "scripts" -- obviously a trivial bit of
Python is more dangerous than a typical piece of JScript in WSH. It's
with the very _existence_ of WSH on a machine. If it's there and
available, it's an easy route for far too many of Windows' past "We
shouldn't really execute this, but hey why not" exploits to find a
loophole between a sandbox that's supposed to be locked down and one
in which a powerful ActiveX can be run unchecked. As a result, it's
just not safe to have it on the machine.
Knute Johnson - 13 Feb 2007 17:17 GMT
>> Out of curiosity, what vulnerabilities does writing your scripts in WSH
>> open you up to that writing your scripts in
[quoted text clipped - 11 lines]
> in which a powerful ActiveX can be run unchecked. As a result, it's
> just not safe to have it on the machine.
And like VBScript it is full of bugs and seriously lacks documentation.
It's different on every platform too.

Signature
Knute Johnson
email s/nospam/knute/