This is really interesting, I've seen this pattern somewhere. IMHO, CoffeeScript had a really similar effect on the development of JavaScript / EcmaScript, but then, it quickly started going extinct. Same with IO.js vs. Node.JS, which was eventually re-integrated into the main line.
It's interesting how apparently sometimes you just need to step aside to break old conventions and demonstrate new capabilities, but eventually, you'll need the support of the community to pull it through: Plus, it's always a gamble. Python barely made it over to v3 after 10 years. I'm not sure if Perl will ever cross the gap or if Perl 6 fragmented the community for good.
Just some random thoughts though on the dynamics of open source, I'm glad for the experience of PHP at the beginning of my career, but I wouldn't touch it or any derivatives any time again having free choice. Too much Heinz™ design: Grown, not made.
These fork-like efforts are able to take the risk of the experimentation without putting the mainline project at risk, and their successes allow the supporters within the original project to point to it as a viable path and gain the needed mindshare to pursue something achieving the same goals.
It's a similar model to larger corporations allowing innovation to occur in startups and then buying them out once the model or technology is proven to a degree.
I think CoffeeScript made transpilers mainstream (though it wasn't the first) and i appreciate that (having a sane language like clojure in your browser is amazing), but damn that syntax was confusing more often than not. Sometimes less is not more.
My thoughts on this from practical experience at Perl conferences and Open Source conferences in general: many (former) Perl 5 programmers are looking forward to finding a use-case to use Perl 6 for a project in their environment. And some have done already, and put the result in production, which may be specifically easy with micro-services using Cro (https://cro.services).
Of course, there are (former) Perl 5 programmers who still think Perl 6 is the sole reason for Perl's demise. These are fortunately very few, but alas also very vocal.
It really boils down to the implementation. Also, you need community support. What really helped HHVM mature is that by using PHP for something large scale, they were able to see its shortcomings. Most other forks are not driven by that. As such, their upsides are questionable, or they just offer some performance boosts, that are achievable even without the trouble of forking.
And honestly the jump from php 5.6 -> 7 is pretty painless.
Its probably the lack of tests for a lot of old 5.6 software that gives people fear of upgrading. php development has gotten a lot better.
It's interesting how apparently sometimes you just need to step aside to break old conventions and demonstrate new capabilities, but eventually, you'll need the support of the community to pull it through: Plus, it's always a gamble. Python barely made it over to v3 after 10 years. I'm not sure if Perl will ever cross the gap or if Perl 6 fragmented the community for good.
Just some random thoughts though on the dynamics of open source, I'm glad for the experience of PHP at the beginning of my career, but I wouldn't touch it or any derivatives any time again having free choice. Too much Heinz™ design: Grown, not made.