Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

Re: Parrot 0.8.0, "Pareto principle" released!

by dragonchild (Archbishop)
on Oct 22, 2008 at 14:57 UTC ( #718770=note: print w/ replies, xml ) Need Help??


in reply to Parrot 0.8.0, "Pareto principle" released!

Is there a sense of how much further we have to go before someone could actually use a language on top of Parrot in production? I'm not asking about P6 specifically, but what about any other language?


My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?


Comment on Re: Parrot 0.8.0, "Pareto principle" released!
Re^2: Parrot 0.8.0, "Pareto principle" released!
by chromatic (Archbishop) on Oct 22, 2008 at 17:56 UTC

    PCT (the tools used to implement languages) and probably Parrot as well need a little more work to namespaces and global storage to allow languages to interoperate without trampling all over each other. Parrot needs its install strategy fixed too in a few ways. Beyond that, mostly Parrot needs some spit and polish -- though PGE (the grammar engine) could use optimization and longest token matching. Mostly people just need time to write languages and file bugs.

      I don't think I asked my question very well. Let's say that I'm looking at a brand-new small application at work for internal use. I've been given complete carte blanche to implement it as I see fit. In fact, my boss is very interested in getting a Parrot-based app in so that we can get some experience with it. I'm going to be using a single language (doesn't matter which one) and I want to just use Parrot as a VM.

      The question is:

      • What language(s) are sufficiently implemented on parrot for internal production use?
      • Is there a list of what needs to be done in order for Parrot to safely support a single language?
      • Would it make sense for the Parrot effort to put some work into polishing those pieces right now?

      Personally, I think having software in a ready-to-ship state as soon as possible makes a lot of sense. I think that it makes even more sense with Parrot because of the "Duke Nukem Forever" tag that has been stamped upon the whole project. If there was at least one language that worked with Parrot and could be used for internal production use, that would go a long way. Then, as more languages are added, it just becomes a rolling boulder.


      My criteria for good software:
      1. Does it work?
      2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
        What language(s) are sufficiently implemented on parrot for internal production use?

        Lua reached feature parity with Lua 5.0 and it's close to 5.1, if I understand correctly. PIR is also stable.

        Is there a list of what needs to be done in order for Parrot to safely support a single language?

        That depends on the language's features.

        Would it make sense for the Parrot effort to put some work into polishing those pieces right now?

        That's what we're doing!

        Personally, I think having software in a ready-to-ship state as soon as possible makes a lot of sense.

        That's why we make monthly releases.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://718770]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (13)
As of 2014-10-20 13:22 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    For retirement, I am banking on:










    Results (76 votes), past polls