Way too late
Larry Wall Unveils Perl 6.0.0
71–80 of 336 posts
Re: Larry Wall Unveils Perl 6.0.0
#72I love Perl [I have been to perl monger meetings and I had to look up how to 'unshift' in python today]. But Python3 is mostly just Python2 with a print function instead of a print keyword. It is occasionally non-trivial to port large existing code bases from Python2 to Python3, but it is practically always trivial for a Python2 programmer to write new code in Python3. I hope Perl 6 will get its own camel book!
> it is practically always trivial for a Python2 programmer to write new code in Python3.
Until you need to use some library that doesn't support python3. I think I've made the transition from python3 to python2 more than I have the other way around.
Re: Larry Wall Unveils Perl 6.0.0
#73Earlier quoted context omitted.
Are you talking about Clojure ;)
As a fan / dilettante of Clojure, I'd say no. The JVM is many nice things, some nasty things, but definitely not lightweight in terms of things like startup speed that I'd expect of Perl 6.
"The JVM is many nice things, some nasty things, but definitely not lightweight in terms of things like startup speed"
The jvm startup speed is actually surprisingly good these days. We were experimenting with writing several commandline tools with Scala, and didn't think they would work because of this "well-known" issue. Turns out it was fast enough even to enable letting Scala handle things like the code completion and still have it feel very snappy.
Re: Larry Wall Unveils Perl 6.0.0
#74Perl was the first programming language I ever used, and i think 6 was being worked on even then. I've moved on to ruby as my goto, but my (limited) memories of perl are fond, and I'm happy to see its still moving forward.
Every time I try and write ruby I end up giving up because the OO is boilerplate heavy and restrictive compared to Moo/Moose. Basically "No method modifiers and I have to write my own constructors? Really?" always drives me away within a few hours.
Method modification is trivially done through "alias" and then just redefining the method in Ruby, if you re-open the same class. If you subclass, then "super" is sufficient. I'm curious what you actually mean here.
As for writing your own constructors, you only need to do so if you actually need to initialize something, and since instance variables can be used without having initialized them in a constructor (they'll just default to nil), I'm curious what you mean here too.
Re: Larry Wall Unveils Perl 6.0.0
#75> ++; # An anonymous state variable, for very fast loops Perl, never stop being you
Also: react { whenever } # Code runs when a condition is met. I can only think this must be a generic https://en.wikipedia.org/wiki/COMEFROM . It is sure going to create some viciously subtle bugs.
INTERCAL finally weeps for joy at being able to claim Perl 6 as a spiritual descendant.
Re: Larry Wall Unveils Perl 6.0.0
#76Earlier quoted context omitted.
Don't worry, within 24 hours there will be hundreds of comments all explaining how Perl 6 is of no interest to anyone.
It does need to find an audience. People using Perl 5.x are probably working in conservative companies that stuck with what worked. Perl 6 will need 2-3 years to bake. Python 3.x is just gaining some tractions 7 years after its release. Perl 6 needs to find a problem that it can solve well. Perhaps a great web framework?
The companies I know using Perl are generally not so conservative - many of them also have Go code bases, heavy focus on DevOps, and so on. They tend to keep using Perl because they have developers who love programming in Perl...
Re: Larry Wall Unveils Perl 6.0.0
#77> One of the most impressive things Larry demonstrated was the sequence operator, and Perl 6's ability to intuit sequences.
say 1, 2, 4 ... 2**32
Someone with more time than me needs to find an IQ test that is based around sequence questions like this and plug them all into Perl 6. So we can find out what Perl 6's IQ is and whether it has achieved AI.
Re: Larry Wall Unveils Perl 6.0.0
#78Seems too little too late. Is Perl still relevant in 2015? What would you build in Perl today that you wouldn't build in another language instead? I used to be a big fan of Perl but it seems to have fallen behind the times, I doubt Perl 6 is enough to catch up.
Too late for what? There is a difference between relevant and trendy. Perl, in many cases, is extremely modern. The Unicode support of Perl 5 is nothing short of state-of-the-art. CPAN is still an amazing resource. The web and OO frameworks for Perl are fresh as ever.
I mean, yeah. We're all going to be using Node.js in another year or two. But that's because our industry is bloody ridiculous. Not because Perl is ill-equipped for the "modern" age (People raving about MVC, the actor model, and promises in 2015 is tiring)
Re: Larry Wall Unveils Perl 6.0.0
#79I honestly did not expect to see the day Perl 6 gets finished. This must have been one of the most difficult - if not the most difficult - births in the history of programming languages. At work, I have been using Perl 5 increasingly often over the past two years, mainly because handling unicode in Python 2 is not a lot of fun (and I still haven't come around to learning Python 3), and I have rediscovered why I used…
> I still haven't come around to learning Python 3 I'm not using it everyday yet either, but it's not a whole new language. More like just a few cleanups to sensitive portions of the API.
I would love to see a concise document with the differences.
Re: Larry Wall Unveils Perl 6.0.0
#80I love Perl [I have been to perl monger meetings and I had to look up how to 'unshift' in python today]. But Python3 is mostly just Python2 with a print function instead of a print keyword. It is occasionally non-trivial to port large existing code bases from Python2 to Python3, but it is practically always trivial for a Python2 programmer to write new code in Python3. I hope Perl 6 will get its own camel book!
> it is practically always trivial for a Python2 programmer to write new code in Python3. Until you need to use some library that doesn't support python3. I think I've made the transition from python3 to python2 more than I have the other way around.
I've been writing forward compatible py2 code for years using the __future__ imports to ensure proper semantics are preserved. When all my external dependencies have py3 support it becomes a breeze to upgrade using 2to3 and the rare occasional manual fixup.