Re^3: JSPL vs JavaScript ...and other questions

I have only looked briefly at JavaScript::Duktape and patched it to also work on Windows, but I haven't had the need to use it in a more involved way.

I also haven't used JE, but as it is an implementation running in pure Perl, it is really slow.

I have used (and written) WWW::Mechanize::Chrome and WWW::Mechanize::Firefox, but if you don't need a browser+DOM, they are vast overkill and likely much more fragile than an embedded VM.

Comment on Re^3: JSPL vs JavaScript ...and other questions

Replies are listed 'Best First'.
Re^4: JSPL vs JavaScript ...and other questions by ptizoom (Scribe) on Jul 20, 2017 at 09:35 UTC
I am dazzled, this busyness has fast evolved. We are such small things. Anyway is it right to seeing two trends to bridge javascript-html and perl : connect directly to the guts of a browser process, using WWW::Mechanize::"my_amazing_browser" and its many engines. interfacing a virtual javascript/ECMA engine within JavaScript::"the_bestest_JS" and then plug it in WWW::Scripter stuffs. ...? and got to say I am impressed by this JavaScript::Duktape looks quite clean, furnished with thorough tests and lush documents, and did installs at first shot, using duktape v2.0 on my debian system (except for this: "CAUGHT ERR: Error: oh boy! at t/nested.t line 18." !).	[reply]
Re^5: JSPL vs JavaScript ...and other questions by Corion (Patriarch) on Jul 22, 2017 at 12:25 UTC
Just now, tobyink has released JavaScript::Any, which claims to offer a unified API among the various choices of (pure) Javascript environments.	[reply]