Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

Re^11: Perl 6: Managing breakages across Rakudo versions

by raiph (Friar)
on Jul 18, 2012 at 20:28 UTC ( #982529=note: print w/ replies, xml ) Need Help??


in reply to Re^10: Perl 6: Managing breakages across Rakudo versions
in thread Perl 6: Managing breakages across Rakudo Star versions

Being free to break things without regard for users both helps and hinders Perl 6 and Rakudo in getting to the next level.

It helps in the sense it lets the designers and implementors move more freely and quickly. The Rakudo compiler is developed in this spirit.

Breaking things hinders Perl 6 and Rakudo to the degree there's a need for many more folk who successfully deploy Perl 6 in a production setting before considering calling Perl 6 "production ready" and folk who might do so are averse to signs of excessive instability. The Rakudo Star bundle is developed for these folk.

To encourage folk to try Perl 6 in production settings, and respond to complaints about rewrites, Patrick considers it necessary to at least have explicit public understanding about managing breakages across versions of Rakudo Star.

(Fwiw I would say the Parrot team made the mistake of prematurely deploying an onerous stability policy but the Perl 6 and Rakudo teams have not.)


Comment on Re^11: Perl 6: Managing breakages across Rakudo versions
Re^12: Perl 6: Managing breakages across Rakudo versions
by jdporter (Canon) on Jul 18, 2012 at 20:35 UTC
    there's a need for many more folk who successfully deploy Perl 6 in a production setting before considering calling Perl 6 "production ready"

    Hard to imagine anyone saying that with a straight face.

Four Legs Good, Five Legs Bad
by chromatic (Archbishop) on Jul 18, 2012 at 22:07 UTC
    ... calling Perl 6 "production ready"...

    If you call a tail a leg, how many legs does a dog have?

    It doesn't matter what you call Perl 6. The fact of it is that, for the foreseeable future, deploying a Perl 6 application will require you to follow the Perl 6 development process pretty closely. Sure, you can get a lot done with the state of either of the two leading implementations—if you're willing to invest the time in an immature product. Sure, there's a renewed commitment to improving the maturity of Rakudo at least.

    Those are all well and good, but a tail is still a tail and not a leg.

      Your summary is in the right ballpark. Your dog dig makes no sense to me. Who's calling Perl 6 "production ready"?
        Who's calling Perl 6 "production ready"?

        If you're going to tell anecdotes about how "real people are using it in production now!" (Re^4: Perl 6: Managing breakages across Rakudo versions), you really ought to disclaim that anecdotes aren't data, that a handful of people don't necessarily make a trend, and that the repetition of the word "production" between your anecdote and the phrase "production ready" is, at best, coincidental (or a deliberate—and as I see it, dishonest—attempt to reframe the debate).

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (11)
As of 2014-07-25 08:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (169 votes), past polls