The most that was ever promised about the 5->6 transition was that there'd be ways of using 5 modules in 6 (which more or less works for 'pure-perl' 5 modules, within reason).
As Larry put it the day he announced it:[1]
> It is our belief that if Perl culture is designed right, Perl will be able to evolve into the language we need 20 years from now. Itβs also our belief that only a radical rethinking of both the Perl language and its implementation can energize the community in the long run.
> (which more or less works for 'pure-perl' 5 modules, within reason)
Are you misunderstanding what has been achieved?
Using the "Best First" view of replies to the 2008 PerlMonks question What defines "Pure Perl"?[2]
> "Pure Perl" refers to not using the C-extensions ("XS") and thus, not requiring a working C compiler setup.
Inline::Perl lets Raku code use Perl modules as if they were Raku modules. XS or pure perl.[3]
Not all of course. Some make no sense whatsoever in Raku (eg source filters). Some don't yet work but could if someone cared to deal with issues that arise. But if you're thinking that Rakudo only imports pure perl modules for the above definition of "pure perl", please know that Rakudo is light years ahead of that due to niner's amazing work. And if you mean some other definition of "pure perl" it would help me if you shared it. :)
[1] https://www.perl.com/pub/2000/10/23/soto2000.html/
I want to know which distro removed perl because that's quite a drastic step and am interested in studying it. Sorry if that offends you.
'look at how perl did things!' is just a really strange approach in a discussion about the Python 2/3 thing. That operation was successful, the patient died.
Biggest of them all. I can't find the announcement.
Compare this to Python 2/3. It's basically an incompatible fork that doesn't add enough for many projects to consider upgrades, and adds the overhead of having to worry about two version. All it really accomplished was guarantee that "Python 4" will never, EVER be a thing.