Perl is 26 Today

Post by nailer » Thu, Dec 19, 2013, 5:55 PM UTC

Mithaldu wrote: post #102

nailer wrote: post #84

Earlier quoted context omitted.

shrug The queue module takes complex data structures, provides them to processes, which when finished doing whatever they do, send them back to other queues and in turn more processes. It works, complex data structures are being shared. There's no nightmarish locking issues. Not sure what else you want. Are you entirely sure you're not discounting the solution because It's Not What Java Does?

I'm sorry if that wasn't clear, sharing doesn't only mean "making the data available" but also means high performance and direct access. Quite simply though: If you can't imagine different use profiles that make certain multi-processing paradigms better suited than others, then you shouldn't be having this discussion and should be getting more experience outside of what you're doing right now.

Post by chromatic » Thu, Dec 19, 2013, 6:11 PM UTC

geophile wrote: post #120

arc_of_descent wrote: post #95

Earlier quoted context omitted.

It prints the greater variable between $x and $y. [$x => $y] creates an array reference. => is just a fancy syntax for a comma. So its actually [$x, $y]. [$x => $y]-> dereferences the array ref. $x Sorry if I'm unable to explain properly! Here's a script. #!/usr/bin/perl use strict; use warnings; my $x = 8; my $y = 9; print [ $x => $y ]->[ $x

- Why not just write ',' instead of '=>'? Is there an actual reason for this other syntax to exist and to be used? - Why does the array have to be explicitly dereferenced? Isn't it obvious from context? - Why count on the mapping from boolean to int being false = 0, true = 1? Pretty much everything other language that has such a mapping does false = 0, true != 0. In one line, a vivid reminder of why I find perl so aw…

Post by drivers99 » Thu, Dec 19, 2013, 6:21 PM UTC

geophile wrote: post #120

arc_of_descent wrote: post #95

Earlier quoted context omitted.

It prints the greater variable between $x and $y. [$x => $y] creates an array reference. => is just a fancy syntax for a comma. So its actually [$x, $y]. [$x => $y]-> dereferences the array ref. $x Sorry if I'm unable to explain properly! Here's a script. #!/usr/bin/perl use strict; use warnings; my $x = 8; my $y = 9; print [ $x => $y ]->[ $x

- Why not just write ',' instead of '=>'? Is there an actual reason for this other syntax to exist and to be used? - Why does the array have to be explicitly dereferenced? Isn't it obvious from context? - Why count on the mapping from boolean to int being false = 0, true = 1? Pretty much everything other language that has such a mapping does false = 0, true != 0. In one line, a vivid reminder of why I find perl so aw…

Post by ChuckMcM » Thu, Dec 19, 2013, 6:28 PM UTC

d23 wrote: post #113

ChuckMcM wrote: post #107

So when I went to Google I learned Python. I enjoyed the language and used it a lot, it has a solid support base and pretty much anything you wanted to do you could import a module to do it. When I went to Blekko they were a perl shop, which was a bit intimidating at first, but after programming in it for nearly 4 years now I find I can get from concept to first test faster in Perl than I could in Python. And I hadn'…

Could you explain what features or aspects made it quicker to get up and running with? I love Python and have never worked with a language that I felt let me get features out so quickly. Do you feel you've sacrificed readability as well? I've heard Perl is notorious for having a million ways to do everything, making reading it hard.

Post by hernan604 » Thu, Dec 19, 2013, 6:37 PM UTC

arunix wrote: post #111

mxey wrote: post #99

Earlier quoted context omitted.

Dancer or Mojolicious are more like Sinatra or Flask, not like Rails or Django

Indeed. Perl does have Jifty and Gantry which do have out of the box support for the M part of MVC, but for whatever reasons they never became as popular as Django/Rails.