JavaScript Implementations

[prev] [thread] [next] [lurker] [Date index for 2006/05/29]

JavaScript -- the new respectable face of the web.  Until you want to do 
anything with it outside of a browser.  There's apparently lots of choice:

* Rhino -- except that loading a full JVM to run a few lines of 
JavaScript code is living using a JCB to swat a fly.
* SpiderMonkey -- Mozilla's JavaScript engine, ripped out and zombie-like.
* njs -- so dormant it's like Rip van Winkle.
* WSH -- yep, that'll work really well on my mac.

All I wanted to do was run JSLint at the command line.  Surely it can't 
be that hard?  Yet SpiderMonkey has no I/O capabilities at all.  Rhino 
has ReadFile(), but it's Java and slow.  njs couldn't even parse the 
bloody jslint source, let alone try providing some input to it.

That's OK, I'll work around this by using JavaScript::SpiderMonkey and a 
small bit of Perl.  Except that appears to hang completely when run 
against the simplest function().  What a steaming pile of donkey turds.

• JavaScript Implementations Dominic Mitchell 22:52 on 29 May 2006
  • Re: JavaScript Implementations Yoz Grahame 01:33 on 30 May 2006
    • too deep to show
  • Chris Nandor 21:11 on 30 May 2006
    • too deep to show

Generated at 08:01 on 31 May 2006 by mariachi 0.52