5 ms·
There's actually talk about amending the name for next major language release ( https://rakudo.party/post/The-Hot-New-Language-Named-Rakudo https://rakudo.party
by zoffix222 9y ago
There's actually talk about amending the name for next major language release ( https://rakudo.party/post/The-Hot-New-Language-Named-Rakudo https://rakudo.party/post/The-Hot-New-Language-Named-Rakudo ). Exactly for the reasons you state: it's a completely different language than Perl and so far it proved too confusing for everyone.
- cygx 9y agoFor what it's worth, I disagree and was a bit annoyed that you've re-opened that particular Pandora's box again ;)
- zoffix222 9y agoI don't mind annoying people to solve problems.
- cygx 9y agoI think you're trying to solve the wrong problem: Don't move the languages further apart through rebranding, move the implementations closer together through improved interoperability. Have a frontend that can invoke the perl5 interpreter as well as Rakudo as appropriate, supporting the perl5 command line flags, and arguably quite a bit of the problem goes away.
- labster 9y agoYou should mind annoying people to cause problems. Bringing up the language naming thing, again after 10+ years of discussion, has all of the problem solving ability of "hay guise whats going on in this thread?" Branding is not the problem with Perl 6, though it is the easiest thing to bikeshed. The problem is compiler speed, language interoperability, and enough of a toolchain to start building serious apps. Make that good enough, and no one will care what our language is called.
- moocowtruck 9y agodunno perl6 seems fine to me, rakudo just looks like something half my team will wonder how to pronounce.. I agree with the other guy that people want a platform that they can use and is performant