For controlling "the browser", that is, Firefox, you only need a TCP connection to the mozrepl plugin. If you want to write your own Javascript-capable browser, then it could be beneficial to reuse a Javascript interpreter written for Parrot, if you tie yourself to Parrot. But the main work of writing a Javascript-capable browser is implementing enough of a credible DOM so that most of the Javascript on a page works.
| [reply] |
That is indeed Parrot's vision for the distant future, but even I as a Perl 6 developer and advocate think that it's far off in the future.
Browsers embed highly specialized and optimized javascript JIT compilers, and a general-purpose dynamic VM like parrot can't really hope to compete in terms of speed any time soon. And since speed is a major concern for browsers, we can't really expect to see wide spread adoption of parrot on the browser level until the performance issues have been sorted out.
| [reply] |
Wasn't there a plan to run Perl 6 on Google's JS engine sometime back. What happened to that?
| [reply] |
| [reply] |
In the "Library for WWW with Perl", (LWP) "wars", Corion's Mechanize::Firefox is like the ultimate "nuclear weapon"!
It is possible to telnet into Firefox (if you have the MozRepl add-on installed) and "drive it around" and that is just way cool! WWW::Mechanize::Firefox uses that interface.
I have no idea of how to run JavaScript from within Perl. The good news is that most of the time, you don't have to do it (actually run the JavaScript). | [reply] |
| [reply] |
