Hacker News Reader

Hacker News

Comment by xupybd | Hacker News Reader

Full thread

xupybd

So is Perl never going to go past version 5 now?

View on HN

As yet there seems to be no solid plan. Context:

http://blogs.perl.org/users/ovid/2019/08/is-perl-6-being-ren...

http://blogs.perl.org/users/ovid/2019/10/larry-has-approved-...

Good question. I has been suggested to use the major version number in the future. Which would mean in May we would see the release of Perl 32.

I would prefer if they created a year alias to the version.

So both of these lines would be equivalent.

    use v5.32;

    use Perl v2020;

Your guess is as good as anyone else's at this point.

I thought the point of the rename was Perl 5 can now release Perl 6 or 7, with Raku being independent.

> I thought the point of the rename was Perl 5 can now release Perl 6

I think that would only add to the confusion, since Perl 6 was already a thing, albeit totally different from Perl 5

They should skip "Perl 6" and go directly to "Perl 7", like Windows that skip "Windows 9" to avoid confussion.

Unfortunately, "Perl 7" was a "thing" in the discussions before the name change. IMO, going to "Perl 32" makes more sense, as it actually reflects the current version numbering scheme. Or refer to the year: Perl 2020.

If Oracle had "bought" Perl they'd probably renamed it to Perl 32 by now and sued everyone else for using sygils.

The current numbering scheme uses odd minor version numbers for development versions and even for stable, just like Linux used to, until Linus got fed up with 2.6 after 8 years. Now it gets a bump whenever the minor version sticks too much.

https://askubuntu.com/a/843247

"Perl 32? But I have a 64 bit processor!"

I remember the "skipping version 9" in windows was due to many developers using "startsWith(os.version(), "9")" (pseudocode obviously) to detect windows 95/99 and therefore they avoid using version 9 in order to remain compatible, but I might remember wrong.

Yes, it is a totaly different type of confussion. More cases https://en.wikipedia.org/wiki/Software_versioning

PHP did the same thing, skipping from 5 directly to 7 because PHP 6 ended up being a dead-end. It was pretty painless (at least as far as I could see).

“A foolish consistency is the hobgoblin of little minds.” — Ralph Waldo Emerson

That is not actually the same thing.

PHP 6 was thrown away never to be seen from again, because it was seen as bad.

Perl 6 was renamed because both Perl 5 and Perl 6 are significantly different active languages.

If Perl went to 7 it could indicate to some that 6 was bad in the same way. That is it would trade one confusion for another.

---

If Perl truly wants to go beyond 5, it should make a major step.

Either by going to the subversion (32), or the year (2020).

Well, the features in Raku ARE what would be (and was) Perl 6. Perl 5 most likely won’t inherit these features as the benefit of Perl 5 IMHO is that it is stable and ubiquitous.

Raku has some pretty amazing things going for it though. It is unique compared to any programming language with its grammars and such.

There's no need to when there are an infinite amount of decimal places.

Reply on news.ycombinator.com