Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

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

by jdporter (Canon)
on Jul 18, 2012 at 01:59 UTC ( #982361=note: print w/ replies, xml ) Need Help??


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

Wouldn't you want to know whether they'd consciously break ...

I might like to know it, but I shouldn't be surprised and wouldn't be heartbroken to learn it.


Comment on Re^8: Perl 6: Managing breakages across Rakudo versions
Re^9: Perl 6: Managing breakages across Rakudo versions
by raiph (Friar) on Jul 18, 2012 at 17:54 UTC

    I think we all agree with Larry's position: no guarantees of stability:

    "Until 6.0.0, there is *no* guarantee of stability. You are all Early Adopters. If you can't figure out how to snapshot a particular version and keep it around, you probably shouldn't be Early Adopting. The whole point of Rakudo * is to give us lots of Early Adopters so we can put lots of final polish onto 6.0.0 as rapidly as possible after that. Don't start asking us to leap across the chasm before we're ready."

    ~~ Larry Wall, March 2010.

    That said, stability (contrasted with a guarantee of stability) is still a significant issue for most Early Adopters. So it makes sense to me that the Perl 6 and Rakudo teams are considering how they might best accommodate those who care about stability; and that Patrick was considering writing a document to formalize stability policy (even if that policy starts with "there are no guarantees of stability!"); and that Patrick was asking for input from users and other interested parties about these issues.

      As usual, Larry cuts to the heart of the matter, brilliantly.

      But, if I may be so bold, I believe you misinterpret him when you focus on a distinction between stability and a guarantee of stability. I believe what Larry is saying is that instability is a fact, things break, you (as a "user") don't know what or when, and as an Early Adopter you're foolish to expect any stability. And therefore, you, as the "vendor", should not be worrying about what your Early Adopters might think about this or that level of stability.

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (11)
As of 2014-07-31 15:39 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (249 votes), past polls