Re^2: Error while installing JE

But none of them are written in Perl :)

Also, the other engines are inconvenient as you need a C compiler, and you need to build them (which might require other tools, like Python). I would assume that Sprout does this for fun, and also because he can, and if it works for others, that's another benefit. Using a Javascript engine written in C is likely faster, but I doubt that that's his point.

Comment on Re^2: Error while installing JE Download Code

Replies are listed 'Best First'.
Re^3: Error while installing JE by vkon (Curate) on Feb 18, 2011 at 22:10 UTC
Also, the other engines are inconvenient as you need a C compiler, and you need to build them (which might require other tools, like Python) yes, I understand this convenience of pure-perl modules over modules that require C compiler This works for simple cases, but not for something real big, like entire programming language Having slow (and memory hungry) pure-perl JS engine, compared to fast V8 or SpiderMonkey, means only one thing - pure-perl is a toy, and v8 or spidermonkey is a real something (o-kay, if not a toy, then maybe this is a reference implementation? but JE is not positioning this) Next, why do you might prefer pure-perl over C, in this particular case? portability? or maybe you want to experiment with source code by adding something to it? Current version number - 0.05x - means that even author expects it to be far from being ECMA standard-compliant - otherwise it would be 1.00 or something. OK, just as another guess - maybe author writes such a module to become familiar with Ecmascript language?	[reply]

Replies are listed 'Best First'.

Re^3: Error while installing JE
by vkon (Curate) on Feb 18, 2011 at 22:10 UTC

Also, the other engines are inconvenient as you need a C compiler, and you need to build them (which might require other tools, like Python)

yes, I understand this convenience of pure-perl modules over modules that require C compiler
This works for simple cases, but not for something real big, like entire programming language

Having *slow* (and memory hungry) pure-perl JS engine, compared to fast V8 or SpiderMonkey, means only one thing - pure-perl is a toy, and v8 or spidermonkey is a real something
(o-kay, if not a toy, then maybe this is a reference implementation? but JE is not positioning this)

Next, why do you might prefer pure-perl over C, in this particular case? portability? or maybe you want to experiment with source code by adding something to it?

Current version number - 0.05x - means that even author expects it to be far from being ECMA standard-compliant - otherwise it would be 1.00 or something.

OK,
just as another guess - maybe author writes such a module to become familiar with Ecmascript language?

[reply]