Hi all, Aza Raskin, the head of user experience at Mozilla labs (http://en.wikipedia.org/wiki/Aza_Raskin), was giving a talk at the BBC today and I asked him about multiple client-side language support.
The short response is that this will not be implemented soon, but it sounded like they were leaning towards the LLVM (http://en.wikipedia.org/wiki/Llvm) to implement this. In fact, Aza seemed to be under the impression that Parrot was a dead project. I asked permission to mail him about this later and he said "yes" (I suspect he might simply have been polite) and I'm wondering the best way to approach this. My first thought (for Parrot devs), one which I know has been discussed before, is about sandboxing Parrot and how to implement authorities for adjusting the sandbox restrictions. My second thought is rather blue sky (and directed at Mozilla, but I'll mention it here) is how this would look on the client side. Here's what I think would be a sample API: <script grammar="http://my.server.com/my/custom/grammar/"; version="1.2" authority="https://my.server.com/grammar/authority/";> include My.Login; Document login_form password matches(SafePassword) or element error("Password must match #{SafePassword}"); </script> In other words, if the sandbox is secure enough, one could use the Parrot Compiler Toolkit to write a set of bindings to allow you to write your client-side in any language you like, include bespoke languages, if desired. I think this could be a very compelling feature and perhaps might pique Mozilla's interest. More to the point, Aza specifically mentioned that he wants to write his client side code in Python. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://use.perl.org/~Ovid/journal/ Twitter - http://twitter.com/OvidPerl Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
