41–50 of 463 posts
Earlier 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?
I think there are plenty of reasons, and they work to reinforce each other.
Earlier quoted context omitted.
Perl5 -> Perl6 has been highly contentious. Perl6 is basically a different language much to the chagrin of many Perl users. A lot of Perl users are entrenched in Perl5. FWIW: I'm unclear why people continue to use Perl at all, I moved on in 2011.
I'm all about using the right tool for the job. Sometimes Perl is that tool, and thus sometimes I'll still use Perl.
Earlier quoted context omitted.
> FWIW: I'm unclear why people continue to use Perl at all, I moved on in 2011. Because it works. Scripts/software that works does not experience bit rot. As long as it works, people will continue to use it. Edit: OK, fine. It seems the downvoters are convinced that the code does in fact experience bit rot, and spoils with time. Probably like fish.
The environment changes, and old programs need to update to keep up with new data formats and remote services and security threats.
What utility does Perl provide in a world dominated by python?
Movable Type is about the only blog framework not written in PHP. If you thought Perl was a bad language, PHP is way, way worse. And Movable Type is also the only one that can use Postgres for storage.
I could not find any blog engine in Python.
This has been a huge deal for the Perl community. First, it was thought that Perl 6 would be the replacement for Perl 5. But it was long ago recognized that there was no clear upgrade path from Perl 5 to Perl 6, so it was agreed that Perl 6 was a "sister" language to Perl 5 rather than the successor. Except that many people expected that Perl 6 would be the replacement, so that stalled many projects. So an "alias" fo…
>including being one of the few dynamic languages with a working concurrency model... Elixir is worth a look. It's a pretty productive little language with a great concurrency model.
This has been a huge deal for the Perl community. First, it was thought that Perl 6 would be the replacement for Perl 5. But it was long ago recognized that there was no clear upgrade path from Perl 5 to Perl 6, so it was agreed that Perl 6 was a "sister" language to Perl 5 rather than the successor. Except that many people expected that Perl 6 would be the replacement, so that stalled many projects. So an "alias" fo…
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.
This has been a huge deal for the Perl community. First, it was thought that Perl 6 would be the replacement for Perl 5. But it was long ago recognized that there was no clear upgrade path from Perl 5 to Perl 6, so it was agreed that Perl 6 was a "sister" language to Perl 5 rather than the successor. Except that many people expected that Perl 6 would be the replacement, so that stalled many projects. So an "alias" fo…
> 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.
Can someone explain to me, for what kinda of new projects would they use Perl/Raku in 2019 at all?
Earlier quoted context omitted.
I'm all about using the right tool for the job. Sometimes Perl is that tool, and thus sometimes I'll still use Perl.
Genuinely curious - and not trying to be a jerk... but where do you find Perl fits well? I can only imagine needing it if I'm stuck on a legacy OS/strictly governed environment where it's the only option I have. (ie: governmental work etc.)
This has been a huge deal for the Perl community. First, it was thought that Perl 6 would be the replacement for Perl 5. But it was long ago recognized that there was no clear upgrade path from Perl 5 to Perl 6, so it was agreed that Perl 6 was a "sister" language to Perl 5 rather than the successor. Except that many people expected that Perl 6 would be the replacement, so that stalled many projects. So an "alias" fo…
> 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.