TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

What to say to "Perl 6 isn't Perl any more"

3 pointsby progalmost 15 years ago

1 comment

tzsalmost 15 years ago
That's a strange article. He's upset at "cranks" saying that Perl 6 isn't Perl anymore. His argument seems to rest on two things:<p>1. There were a lot of changes from Perl 4 to Perl 5, and people didn't say that wasn't Perl any more. So, a lot of change from 5 to 6 is the same.<p>2. Larry says it is Perl.<p>The second argument works, at least--Larry is the one with the naming rights.<p>However, the author states this:<p><pre><code> There are those who will read this and say "Yeah, but Perl 5 could still pretty much run any Perl 4 program, but Perl 6 won't be able to run Perl 5." And that's true. </code></pre> That seems to me to be a pretty fundamental difference between the 4 to 5 step and the 5 to 6 step. With 4 to 5, essentially a bunch of new features became available, and you could start adding them incrementally to your existing programs.<p>It sounds like 5 to 6 is, practically, from the programmer's point of view, no different than a transition from Perl to Ruby, or Perl to Python, etc.. That is, it involves learning a new language (and if Perl 6 won't run Perl 5 code than it <i>IS</i> a new language, despite having the same name), and writing new code for it or porting old code.
评论 #1582029 未加载