Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Re^2: MoarVM update

by raiph (Chaplain)
on Sep 10, 2013 at 04:41 UTC ( #1053156=note: print w/replies, xml ) Need Help??

in reply to Re: MoarVM update
in thread MoarVM update

To be clear, no one should hold their breath for Perl 6 on MoarVM. Based on what I know, I'd guess that MoarVM will run Rakudo Perl 6 enough to compile and run itself before YAPC::NA 2014 in 9 months. Of course, it might never happen. We shall see.

Jan 8th, 2014 update: A Rakudo on MoarVM update

In the meantime, if anyone reading this is interested in helping build MoarVM, join the IRC channel #moarvm on freenode and have a chat.

Replies are listed 'Best First'.
Re^3: MoarVM update
by Arunbear (Parson) on Sep 11, 2013 at 10:08 UTC
    That raises the question: what is the point of MoarVM (i.e. if not to run Perl 6)?
      The original and current justification for developing MoarVM is to run Perl 6. I didn't mean to suggest otherwise.

      That said, now you've raised the question of the point of MoarVM, I'm not comfortable leaving the foregoing as the complete answer because imo MoarVM is relevant to P5, ignoring P6.

      First, note that there's a "P5interop" project that is starting out by embedding libperl in MoarVM. This will allow Perl 5 code to call "Perl 6 code" and vice-versa. (Sept 2014 update: See the new Inline::Perl5. This embeds libperl, is known to work with Rakudo HEAD on MoarVM, and is expected to work with other backends in due course.)

      Second, note that "Perl 6 code" can include any code from any language compiled using a compiler written in Perl 6. If someone wrote a python compiler in P6, python code could call P5 code and vice-versa. In this scenario, P6 would be a behind-the-scenes implementation detail.

      Third, note that there's a "v5" project, a new implementation of "pure" Perl 5. The "pure" means no XS. But don't forget the P5interop project mentioned above.

      In summary, to more fully answer your question given my own personal view, the original and current justification for MoarVM development was and is to run Perl 6, but the outcome is set to include a reimplementation of Perl 5 with Perl 6 as an implementation detail (or as a side-benefit, if someone prefers to see it as such).

        Hooray, it is fun to announce things that don't exist! Perl-6 is set to allow cold fusion! Perl-6 is set to demonstrate the existence of extra-terrestrial life! Perl-6 is set to negotiate a peace settlement between Palestine and Israel! Bibi Netanyahu recently visited #perl6 and said "Who the #$(* is Raiph and why is he quoting me?" Recently also Anonymous Monk declined to visit #perl6 and said "Raiph never answered the simple yes or no question in Re^13: A $dayjob Perl 6 program that runs 40x faster on the JVM than on Parrot," which just proves that Raiph is set to talk about anything except the truth.
      Finishing things is hard! Let's start new things!
        Rakudo Perl 6 on Parrot is too many years away from being sufficiently ready.

        Are you suggesting some folk should work on Parrot to make it acceptable for 6.0.0? Who? How?

        jnthn decided Perl 6 on JVM was the quickest way to get Perl 6 on to a mature VM so they could drive the Perl 6 specification toward 6.0.0.

        Do you think he was wrong?

        Perl 6 on JVM might be a decent choice for driving the Perl 6 specification toward 6.0.0, and might even be workable for some JVM fans, but it's obviously inappropriate as the only serious VM option. So now what?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1053156]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (4)
As of 2017-04-28 15:12 GMT
Find Nodes?
    Voting Booth?
    I'm a fool:

    Results (525 votes). Check out past polls.