in reply to Perl 6--not just for Larrys anymore

Dang. This is incredible. I've been "sort of" keeping track of Perl 6 development, but this is much further along than I expected. I have a question, though. Parrot has always struck me as beng similar in concept (but not implementation) to the Java bytecode model. Implementation differences aside, how accurate is that? I'm also wondering how easy it is likely to be to mix the languages? Since they compile to parrot bytecode, can Ruby call Perl call Python? Ruby and Python both deserve wider audiences. It seems to me that being able to take advantage of a common bytecode model should be able to give them the edge they need to truly earn their place amongst "serious" languages.

It seems to me that Perl 6 will be powerful enough that the desired features of those other languages (continuations, coroutines, iterators, etc.) will not be much of a pull towards them. However, being able to utilize pre-existing libraries already written in another language should appeal to the virtue of 'laziness'.

Side note: I heard a rumor that here in Portland, Oregon, there was a company that was advertising for Ruby programmers but wound up switching to Python due to the lack of available Ruby programmers. I don't know the particulars, though.

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

  • Comment on Re: Perl 6--not just for Larrys anymore

Replies are listed 'Best First'.
Re: Re: Perl 6--not just for Larrys anymore
by Elian (Parson) on Aug 16, 2002 at 20:35 UTC
    The parrot VM is in some ways like the JVM. One of the central design goals is to make it possible for the various languages running on it to call each other properly, and seamlessly. Which means that your perl proram will be able to call routines written in Ruby, Python, Java (yes, really), .NET code, APL, or even INTERCAL. One of the joys of a standardized calling convention. (And mandated thunking layers to wedge in languages that wouldn't otherwise play ball)

    Oh, and Intel hired python people instead of Ruby ones? Pity.

      Would that intel postion happen to be this one mentioned on jobs.perl.org (Intel/Oregon/Ruby??) If so, could they not find perl programmers either?

      p.s. I checked out parrot and am quite impressed. The mandelbrot example is pretty nifty too. ;-)

      -Blake