When Python did the migration, it had a good flow of new investments coming into it and delivered good reasons for why those should go to Python 3 rather than 2. At the same time, it also already had a base of existing investments in Python 2 delivering better ROI without the added cost of a migration, and the sum of that exceeded the critical mass it took to make it economical to keep both versions of the ecosystem around.
With Perl you are seeing what it looks like when you have zero new investments coming in and no good reasons for why new investments should go to Raku. (Because: Just use Python). You do still have a non-negligible base of existing investments in Perl 5 and those deliver better ROI without the added cost of a migration. So my prediction is that Perl 5 will stick around, and Raku is dead on arrival.
With Nim it might be the other way around: Good reasons for why new investments should go to Nim 3 rather than Nim 2, and not all that much existing investment in Nim 2. If Nim 3 sees healthy adoption, it might well be more economical to re-deploy ecosystem maintenance to Nim 3 and migrate most of the existing code, rather than keep two versions of the ecosystem going.
Perl 5 and Perl 6 (Raku) are different languages.
The migration was no easy task. So all the projects already written in Python 2 remained on version 2. Until the day they reached a dead end and were forced to migrate.
Except for no longer being confused about whether I was reading bytes or "strings" (Python3 eliminated that confusion), and having to remember for roughly a year to use "()" when using print, I don't believe I even really noticed that big a difference between the two.
Honestly - I'm surprised that python managed to hold on long enough for "uv" to be released and solve all the packaging/venv pain - that was a real problem with python for 15+ years and wasn't solved until 2024.