To clarify, this is not an RFC on how to improve Moose. We are already doing that, it's called MooseX and it's doing the job just fine.
As always, after a feature is fleshed out a feature as a MooseX module we decide on whether or not to include it. If you want to propose a feature, do it that way =) I'm talking about the other half of progress, letting go of past mistakes in a way that allows us to do the first part more easily and more dramatically, without hurting existing code in the ecosystem. The points that John raised are all either existing MX or potential MX that are simply too much trouble to code right not because they propose doing something radically different, but that's no excuse for not trying them out as extensions beforehand. The problem is simply that right now extensions need work along side lots of baggage, and that's difficult.
