Perl 7 is going to be Perl 5.32, mostly • Hacker News Board

Re: Perl 7 is going to be Perl 5.32, mostly

#571

Post by igouy » Sun, Jun 28, 2020, 6:58 PM UTC

yellowapple wrote: post #253

continuational wrote: post #17

Earlier quoted context omitted.

What do you mean by efficient and cheap? It doesn't fare well in https://benchmarksgame-team.pages.debian.net/benchmarksgame/... at least.

Depends on what you mean by "fare well". Even in those benchmarks, Perl seems to have a lower memory footprint than Node.js in most of the results. It's also worth noting that three of the examples (pidigits, reverse-complement, fasta) don't seem to do any multiprocessing in Perl whereas they do in Node.js. At least for reverse-complement and fasta, it should be possible to rewrite those to use multithreading (like t…

> should be possible to rewrite those

Until someone does…

Re: Perl 7 is going to be Perl 5.32, mostly

#572

Post by Lazare » Tue, Jun 30, 2020, 9:10 AM UTC

throwaway777555 wrote: post #472

Lazare wrote: post #403

Earlier quoted context omitted.

I feel you. I'm currently at a startup that, somewhat by accident, ended up writing their backend in PHP. Modern PHP is actually fine; it's largely avoided the issues perl has; adoption of the latest versions is quite high, and it's...fine. Not the best, not the worst, broadly comparable to other languages, and a far, far, far cry from what most people may think of when they hear "PHP". My last job used Node, the one…

My experience has been the opposite. I work in a PHP shop and with each new version update, a handful of us are excited about the new changes that get made to the language. Our DevOps team has been on top of keeping our servers running the latest production-ready versions of PHP. So many of the refinements are a welcome change. I'm eager for stronger type hinting and other features that are still coming down the pipe…

No, that's our experience too. We're excited by the changes, eager for each new release, and enjoy being able to write solid code without the language getting in the way (much). When 8.0 drops we'll probably have cake.

...the issue is the community, and (especially) the pool of applicants we get. It may be different where you are, but around here you advertise for a "senior backend dev", and you get a bunch of people with solid experience in, mostly, Python showing up, with maybe a sprinkling of .NET and Java. (Two of the biggest IT employers in town use Python, which skews things a bit, I know.) But you advertise for a "senior PHP dev", and you get all sorts, but (so far) no one we'd consider hiring. (Let me put it this way: The next time one of the "PHP devs" we shortlist turns out to have ever written a functioning unit test will be the first time. And these are people with years of experience, applying for a senior role...)

Re: Perl 7 is going to be Perl 5.32, mostly

#573

Post by tyil » Tue, Jun 30, 2020, 9:20 PM UTC

zem wrote: post #484

deckard1 wrote: post #383

Earlier quoted context omitted.

> perl has been the same since 2002 if you ignore perl 6 then you might as well ignore python 3. And even still, python 2 is dead. There are only a handful of languages as well maintained as Perl 5. https://en.wikipedia.org/wiki/Perl_5_version_history Perl maintains strict backwards compatibility. I can run code that was written decades ago. I really am curious what features you think Perl 5 lacks. > Another issue is…

> I really haven't seen a single thing Python, Ruby, or PHP have done that much better. explicit function signatures for one!

Perl has had those since 5.20, although they're optional.