in reply to Re^2: Perl 6: Managing breakages across Rakudo versions
in thread Perl 6: Managing breakages across Rakudo Star versions
I'm all for Rakudo improving the experience of deploying and maintaining serious code, but it's disingenuous to hand-wave away any differences between "some people are doing this with it and they don't mind babysitting their code between releases" and "you should take this seriously because it's ready for deployment like any other mature piece of software you might expect".
I've been burned before. Rhetorical flourishes and linguistic contortions to redefine away objections won't convince me that I can ship a project built in Rakudo to paying customers (without losing money on support) because people have good intentions now, or Larry wrote a message somewhere.
When the Rakudo developers meet the commitments they've made and demonstrate that they can continue to meet those commitments, I'll take
themthose commitments seriously.
Edit to add: I mean that last paragraph sincerely. I believe everyone involved is acting in good faith. All I mean is that I'm not going to be an early adopter.