|
Re: TimToady Approved renaming Perl6 to Raku
by tangent (Vicar) on Oct 12, 2019 at 00:47 UTC
|
| [reply] |
|
|
If by lively you mean that most comments are from people who don't know much if anything about perl, sure
| [reply] |
|
|
| [reply]
[d/l] |
|
|
For what it's worth I am actually happy this happened. I think It allows Perl 5 to evolve in its own right, as the original language, and who knows at some point become Perl 6 but based on Perl 5, or perhaps skip to Perl 7 just to make historical point.
In retrospect (as usual it's easier to connect the dots going backwards), believe this should have been the best solution from the start because Perl 6 is really a spin-off and not actually a new version of Perl 5. Perl 6 is not, and has never been, the same language.
Anyway, my point is that this renaming is very positive for BOTH the Perl 5 community and the adoption of Perl 6 in it's new name. For the people that continue to love Perl 5, like myself, we no longer have the pressure to migrate to Perl 6, fearing that Perl 5 would eventually end. For the Perl 6 folks, it allows them to attract new programmers to this great language without having to explain that is actually a NEW language.
| [reply] |
|
|
Calling it "Perl++" would have done most of this with far less costs and damages.
But that's their decision which I have to respect.
Anyway the Perl 5 community must now present a concept for the future, and can't rely anymore on blaming Perl 6.
| [reply] |
|
|
Re: TimToady Approved renaming Perl6 to Raku
by FreeBeerReekingMonk (Deacon) on Oct 14, 2019 at 00:21 UTC
|
What is your stance about version numbering?
Is Perl version 6.0.0 too confusing now and will we be having a jump to Perl 7.00.0, not unlike PHP?
Or is it better we have a perl 5.32.0 and greater? And only after a mayor change, switch to a higher version?
use classic_perl; # enable backwards compatibility by disabling modern
perl -E '@_=split//,`cal 1`; say @_[37,38,576,86]'
| [reply]
[d/l]
[select] |
|
|
We can do like Java, which will remain Java 2.x for ever, but actually dropped the 2. So that'll be perl 32, perl 33, etc.
| [reply] |
|
|
| [reply] |
Re: TimToady Approved renaming Perl6 to Raku
by LanX (Sage) on Oct 12, 2019 at 13:12 UTC
|
| [reply] |
|
|
From Why I’m Learning Perl 6:
"It’s funny, fifteen years ago everyone was saying how Perl was shooting itself in the foot with a massive language redesign, because the world was clearly going to switch to Python and Ruby. Well everyone did switch to Python and Ruby, but now everyone’s got the itch to switch again because it turns out Python and Ruby weren’t designed for concurrent code execution. Maybe shooting yourself in the foot isn’t such a bad strategy, if what you need are bionic robo-feet."
"Concurrency is hard and if you want M:N thread multiplexing (i.e. WEB SCALE CODE, where application threads aren’t pinned to pthreads) your options today are precisely Erlang, Go, .NET, and Perl 6."
https://www.evanmiller.org/why-im-learning-perl-6.html
| [reply] |
Re: TimToady Approved renaming Perl6 to Raku
by Anonymous Monk on Oct 16, 2019 at 12:31 UTC
|
Just wondering, where's that "ancient wisdom" from? Is that a Biblical quote? (I don't know the Bible that well, but clearly Larry does.) | [reply] |
|
|
| [reply] |
|
|
| [reply] |
|
|
| [reply] |
|
|
| [reply] |
|
|
|
|
