Earlier quoted context omitted.
Yeah, with Perl 6 out of the way, they would have had 15 years to clean up the syntax of Perl 5 so it was no longer indistinguishable from line noise.
IMHO Perl's reputation for noisy code is mostly the result of code golf examples online and denoting variables with an explicit type character. A sanely written Perl program is nowhere near line noise. Compare to supposedly beautiful languages like Rust and the ratio of punctuation characters to alphanumeric is pretty much on par.
Larry Wall has approved renaming Perl 6 to Raku
161–170 of 463 posts
Re: Larry Wall has approved renaming Perl 6 to Raku
#162Earlier quoted context omitted.
Heh yeah, totally. The only Perl I use these days is oooooooold software (MRTG) I guess with the exception of Spam Assassin and RT...
Ugh. Spam Assassin is so astronomically inefficient and power hungry, that there should be a cryptocurrency based on Proof of Spam Assassination.
Re: Larry Wall has approved renaming Perl 6 to Raku
#163Earlier quoted context omitted.
Sure but there's a reason that development has moved off of Perl.
And other people love chasing new shiny things. I'm yet to see another language ecosystem that solves 99.99% of the problems one might have the way CPAN does. Would I write an API in perl? Nope. Would I write something that massages the data that APIs spit out and processes it, drops into a queues, generates jobs, etc? Absolutely. Mostly because I will write a few hundred lines of code for existing CPAN modules to so…
Yes, Perl's threading support is terrible, and I do wish it was as effortless as in Raku. But you'd be surprised how often you actually only need an event loop and non-blocking implementations, and for the rest of the time there's Mojo::IOLoop->subprocess or IO::Async::Function to provide a thread-like model with efficient forking.
Re: Larry Wall has approved renaming Perl 6 to Raku
#164Earlier quoted context omitted.
> Larry has now agreed with the change and Perl 6 will be renamed to "raku" and Perl 5, which has regular, major releases every year, will now be able to simply be "Perl" and be free to continue on its own way. I hope that doesn't mean that when Perl needs a major number version change again, they'll chose 6. It would be pretty confusing to have 2 Perl 6.
Since the language-previously-known-as-Perl6 will be known as Raku, there shouldn't be any conflict with Perl v6
Re: Larry Wall has approved renaming Perl 6 to Raku
#165Earlier quoted context omitted.
Heh yeah, totally. The only Perl I use these days is oooooooold software (MRTG) I guess with the exception of Spam Assassin and RT...
Man - MRTG... I just had flashbacks to my youth. Loved that piece of software and used it for close to a decade! Anymore Grafana backed by InfluxDB w/Telegraf is my jam for the same general problem set (TIG stack).
RRD is pretty efficient so I don't have much need to change.
Re: Larry Wall has approved renaming Perl 6 to Raku
#166Earlier quoted context omitted.
When someone says they want to work in Perl6/Raku, they likely have vastly different problems than someone using Erlang/Elixer. There is overlap of course (both general purpose), but I can't imagine using Erlang for scripting, while Raku is first class here.
I'm trying to understand, what kind of scripting requires first-class concurrency that isn't fulfilled by say Python?
Re: Larry Wall has approved renaming Perl 6 to Raku
#167Call me a pessimist, but its too little too late... I learned regex in perl so the language will always have a soft spot in my heart. But Python has trounced Perl for almost any task. There simply is no reason to learn perl unless youre in the unfortunate position of managing some legacy stack.
> But Python has trounced Perl for almost any task. Well, I think Perl beats Python in quick and concise one-liners written from the command line, doesn't it? Not that I know much Perl, though.
Re: Larry Wall has approved renaming Perl 6 to Raku
#168Earlier quoted context omitted.
Sure but there's a reason that development has moved off of Perl.
> Sure but there's a reason that development has moved off of Perl. Why don't you specify this single reason you allude to?
Re: Larry Wall has approved renaming Perl 6 to Raku
#169Earlier quoted context omitted.
> Larry has now agreed with the change and Perl 6 will be renamed to "raku" and Perl 5, which has regular, major releases every year, will now be able to simply be "Perl" and be free to continue on its own way. I hope that doesn't mean that when Perl needs a major number version change again, they'll chose 6. It would be pretty confusing to have 2 Perl 6.
Ditch the major version. As the current one is 5.30, the next one will be Perl 31, the next stable is Perl 32.
Re: Larry Wall has approved renaming Perl 6 to Raku
#170Earlier quoted context omitted.
> Larry has now agreed with the change and Perl 6 will be renamed to "raku" and Perl 5, which has regular, major releases every year, will now be able to simply be "Perl" and be free to continue on its own way. I hope that doesn't mean that when Perl needs a major number version change again, they'll chose 6. It would be pretty confusing to have 2 Perl 6.
It's not uncommon to leap frog versions in such cases. PHP went from 5 to 7, for instance.