Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Perl 7 is going to be Perl 5.32, mostly

perl.com

Post reply on HN
Print view View original

151–160 of 573 posts

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

#151

Post by freedomben »

staycoolboy wrote: post #116
jes5199 wrote: 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…

Perl was my first encounter with regular expressions. To this day, no language I've used does it better and cleaner. This includes Python, Boost/C++, Java, JavaScript, LISP, Go and Rust.

Awk and Ruby aren't on your list, any experience with those that you could compare/contrast with Perl?

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

#152

Post by cutler »

boring_twenties wrote: post #134
jwr wrote: post #130

Much as people complain about Perl, it is the language which I use when I want to have something which will run 10-20 years from now. I recently wrote a consistency checker for file archives (so that I know when bitrot sets in) in Perl, precisely because I want it to be usable for a long time ( https://github.com/jwr/ccheck ). Very happy to see a path forward for Perl 5.32.

Perl is still unmatched for one-liners, and by extension, one-liners that graduate to short scripts.

Yes, of all the Perl books in my collection Tim Maher's "Minimal Perl" (Manning) is still the one I dip into regularly.

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

#154

Post by 7thaccount »

jes5199 wrote: post #48
sumanthvepa wrote: post #24

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…

The Moose library is a pretty advanced OO library that was inspired by Common Lisp's CLOS & Smalltalk I think. Most Perl developers I know use a large amount of libraries as the language itself is lacking in many areas. A lot of people are fine with that, but I prefer kitchen-sink languages which are fairly opinionated.

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

#155

Post by Ovid »

As a short summary about Perl 7:

If your Perl is old-school, that's OK. Use Perl 5 and we'll keeping supporting you.

If you your Perl isn't old-school, use Perl 7 and get new features.

If you're not sure, ask us and we'll hold your hand to help you understand.

We're here to make sure you're OK.

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

#156

Post by frakkingcylons »

banana_giraffe wrote: post #2

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.

A lot of Debian's packaging tools are written in Perl.

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

#157

Post by jlokier »

foobar_ wrote: post #64

This is just bad maintenance. Just pick all the stuff people are complaining about and fix it! 1. Improve threads 2. Improve C API support 3. Give local::lib, cpanm by default ... multiple perl versions by default 4. Give direct support for coroutines / async await 5. Mark experimental features as non-experimental (attributes, signatures) 6. Pick an OO system, package system 7. Make switch cool again 8. Get more core…

Just a little note, Perl 5 actually has (in my opinion) excellent coroutines in the form of the "Coro" module hierarchy. Good enough to run a web service on.

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

#159

Post by kungtotte »

jlokier wrote: post #139
kungtotte wrote: post #122

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.

And even in that case it predates all the other languages except Python by almost a year (Python 1.0 came out in January 1994).

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

#160

Post by anthk »

peterwwillis wrote: post #85
jes5199 wrote: 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…

> You learn perl, and you've learned nothing but Larry Wall. Yes, this is why it's nice. You don't have to worship at the foot of an industry which slavishly tries to implement a misunderstanding of a system some dude made up 40 years ago to get around problems in other systems some other dudes made up before that. It's weird on purpose. And it's backwards-compatible-crufty on purpose. Today I can run Perl code writt…

TCL, but 7.x code may have flaws.
Post reply on HN