Live data from Hacker News

Perl 7 is going to be Perl 5.32, mostly

perl.com

231–240 of 573 posts

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

#233

They last line of the article summarizes it well: > Perl 7 is v5.32 with different settings. Your code should work if it’s not a mess. Expect a user release within a year. Are there actually people that are still deploying new things in Perl? The only times I see it is for legacy stuff, and then only because the script is too much of a hassle to be rewritten.

I wrote a quick perl script earlier today to push crt.sh results for a bunch of domains into slack.

Took about 30 minutes, far less time than messing about with why pip has broken on my desktop yet again:

  Traceback (most recent call last):
  File "/usr/local/bin/pip", line 11, in 
    sys.exit(main())
  File "/usr/local/lib/python3.5/dist-packages/pip/_internal/cli/main.py", line 73, in main
    command = create_command(cmd_name, isolated=("--isolated" in cmd_args))
  File "/usr/local/lib/python3.5/dist-packages/pip/_internal/commands/__init__.py", line 96, in create_command
    module = importlib.import_module(module_path)
  File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 986, in _gcd_import
  File "", line 969, in _find_and_load
  File "", line 958, in _find_and_load_unlocked
  File "", line 673, in _load_unlocked
  File "", line 665, in exec_module
  File "", line 222, in _call_with_frames_removed
  File "/usr/local/lib/python3.5/dist-packages/pip/_internal/commands/search.py", line 18, in 

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

#234
post #48

Earlier quoted context omitted.

huh. I spent a couple years writing perl professionally, I guess that was around 2006, and I couldn't agree less. Its object system is so bizarre compared to any other language - it's like it doesn't really have an object system, it has parts of a system that you can try to assemble, but no matter what you do you end up with something weird. And on top of that, the sigils, refs, and `wantarray` systems means that fig…

I think you should revisit perl. My first job writing perl was in 2005 or 2006, and it was not a good language for an eager idiot without guidance. After a couple years, I started getting it, and it became one of my favorite languages. I think it was my coworker who told me to read https://hop.perl.plover.com/ and it blew my mind and made me start to rethink how I was approaching code. With the languages that I'd bee…

Do you have a good link to learn about grammars in perl?

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

#235
post #48

I was part of a team that wrote significant parts of Amazon's payment processing systems in Perl in the late 90s. I really loved the language. It's object system was so flexible and powerful. Once you understood how write idiomatic perl. It was a joy to use. I'm looking forward to trying out Perl 7.

huh. I spent a couple years writing perl professionally, I guess that was around 2006, and I couldn't agree less. Its object system is so bizarre compared to any other language - it's like it doesn't really have an object system, it has parts of a system that you can try to assemble, but no matter what you do you end up with something weird. And on top of that, the sigils, refs, and `wantarray` systems means that fig…

On the subject of transferrable knowledge, Perl was the first language I learned, and I was always a little bit confused about why every language I learned since then didn't have pronouns, until finally magrittr came along in R and made perfect sense to me, since "." in magrittr/dplyr feels a lot like "$_" (or "@_") in Perl.

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

#236

Earlier quoted context omitted.

I think it was really Perl 6 that killed it. Perl had a significant lead over Python, and the Perl 6 announcement just sucked the life out of it.

So it's the Osborne effect? Where you stop using Perl 5 because you're waiting for Perl 6 (announced in 2000, released never? As Raku? As a rolling release? The history appears confusing in Wikipedia.) https://en.wikipedia.org/wiki/Osborne_effect

Perl 6 had its first official release in December 2015. It has since been improved, mainly in performance and in async / event driven capabilities. It got renamed to Raku last year (https://raku.org using the #rakulang tag on social media). You can check out the Rakudo Weekly News if you want to stay up-to-date: https://rakudoweekly.blog

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

#237
post #149

Earlier quoted context omitted.

IMDB was written in Perl, notoriously. Seeing that the layout has not changed in ages, I can only assume it's still Perl. I'd imagine a bigger rewrite effort would have led to a more slick iteration on the UI, and it seems the legacy HTML templates are still baked in.

DuckDuckGo's also written in Perl, and doesn't seem to have any trouble maintaining a reasonably-modern-looking UI.

Booking.com is also (notoriously) completely written in Perl.

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

#238
post #35

Earlier quoted context omitted.

Yes... We have some high revenue, important contract type systems written a long time ago and maintained by the same subject matter experts who simply move the codebases (old and new) to newer systems and stacks. As you can tell, the SMEs have no interest in learning other things and so any new initiatives that require them to implement it is subject to their preferences.

Many places don’t support antifragility. Having an old system that nobody wants to rewrite may not be a reflection on the engineers. You’re an expert, and a rewrite is going to expose you to a lot of scrutiny. You are going to break things, when maybe you haven’t broken things in a long time and people like it that way. So when some day arrives where a new fad is hot and it’s hard to impossible to find Perl programme…

There are plenty of silly reasons to rewrite a piece of code, but language preference has to be one of the worst.

Now that I think about it, that's actually a decent hiring test:

Tell the candidate part of their job will be maintaining a small Perl codebase. If they can't deal with that without throwing a fit, I have no interest in working with them.

It's a sharp tool, if you're not careful someone might get hurt. But professionals deal with sharp tools all the time, especially when it's the best tool for the job.

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

#239

Earlier quoted context omitted.

Perl 5.0 was released towards the end of 1994. Python 1.2 was released in 1995. The first public release of Java as 1.0 was in 1996. JavaScript appeared in 1995 as well, but the first ECMAScript standard didn't appear until 1997. First release of PHP was in 1995, same with Ruby. Perl pre-dates the initial release of all those languages and was already up to its fifth major version by that time.

To be honest Perl 5 isn't really like Perl 4. They are quite different languages - Perl 4 didn't have objects, and Perl 5 places heavy emphasis on them. Up to you to decide when you think it started, but I'd say the current language we think of as "Perl" started with the release of Perl 5.

PHP has object since v3 ('97).

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

#240

Earlier quoted context omitted.

Not a Microsoft fan, but simple C / Windows API code from 25 years ago would likely compile and run on Windows 10 unchanged. My limited experience with Swift suggests that even 25 hours ago could be a tall order...

Moreover, a Windows .exe compiled 25 years ago will also likely just run.

Just run a 20 year old binary and worked fine; I'ld lie if I said it didn't impressed me
Post reply on HN