Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

Re^5: regarding intolerance to perl which I observe

by Your Mother (Archbishop)
on Aug 01, 2013 at 07:08 UTC ( #1047371=note: print w/replies, xml ) Need Help??

in reply to Re^4: regarding intolerance to perl which I observe
in thread regarding intolerance to perl which I observe

What do you see as the radically new features Go and Scala have? And what do you see as possible with Perl6, in theory, that isn't possible with Perl5?

  • Comment on Re^5: regarding intolerance to perl which I observe

Replies are listed 'Best First'.
Re^6: regarding intolerance to perl which I observe
by fisher (Priest) on Aug 01, 2013 at 15:47 UTC

    well, I think I can answer that question of yours since I agree with what previous orator has stated.

    I personally don't know Go nor Scala, but I know Erlang and a bit of Haskell. Well, everything you can do in Erlang you can also do in perl, but! But some things will be easier to do in erlang, for example, to spawn a pool of thousands of processes for almost every client.

    If you need an example of the radically new feature -- how about the well-known statement that 'if it compiles, it works'? This became possible because of strict typing plus pure functional approach in haskell. And in perl we still teaching newcomers to append those silly 'use strict; use warnings' lines in every single script.

    I personally feel the lack of pure functions in perl. I like the idea of *guaranteed* absense of side-effects when it is not otherwise stated. I like to spawn a lot of isolated workers as simple as a *click* by two fingers. And no worries about threads and shared data and all that scary stuff -- we have actors communicating with each other by sending messages to each other. 'Everything is a process' can be a motto for erlang.

    But despite of all that said above there's still a niche for perl. When I want, for example, to analyze the web server's output, or gather some data from logfile or even do some sketch on 'how it should work' using FCGI + nginx -- I don't know the better tool than perl for these kind of task.

    Well, soething like that.

      The operative term in the original statement and the follow-up question being "new." Haskell is almost the same age as Perl, as is Python and Ruby is just a few years younger. Either these things were always a better choice than Perl and Perl's success is just some bizarre aberration or Perl is still just as valid a choice. And Erlang is optimized for a very specific use case. I wouldn't attempt to use perl to parse client side DOM either. I looked at Scala the smallest bit a couple years ago and nothing leapt out to distinguish it. On the contrary, it seemed Perl-like without as much flexibility. Which obviously some feel is a strength. I disagree.

      Use Perl for what you want. Call it a niche tool if you prefer. If you find general attitudes to Perl to be "it's no good," don't expect your attitude to do anything but cement the views. Well, sure it's okay for prototyping web stuff but why go to all the trouble to learn such a messy, goddawful language just do hello world in a webpage? I mean, you can parse a log file with awk."

      I use strictures or equivalent in scripts. I also write one-liners all day. If I had to qualify variables and namespaces and return values and… for them, I'd start looking for another tool. Perl lets you be a lousy hacker without complaint, it's true, but it also doesn't get in your way at all when you know what you're doing. Professional tools have fewer safety features than kids’ toys and institutional, packer-oriented workflows.

      Happened across this yesterday right after commenting in this thread and it seemed very pointed to me–

      With regard to the “wrong equipment” … Unlike most musicians, Josh Homme doesn’t just dabble in a bit of engineering when necessary, but has a genuine love for the métier. “I love [music] engineering… …I found over the years that if everyone is using something, it can’t be that good!”

      "If it compiles, it works" is a pipe dream. "If it compiles, then it will do something" is probably the best we can hope for. Strong typing isn't enough to prevent logic errors.

      package Cow { use Moo; has name => (is => 'lazy', default => sub { 'Mooington' }) } say Cow->new->name
Re^6: regarding intolerance to perl which I observe
by curiousmonk (Beadle) on Aug 03, 2013 at 03:49 UTC

    In theory anything possible in one language is possible in other languages too. But by that argument you could also say anything possible in perl, can be done in C. Going by this line of argument, we may have to settle with using NAND gates.

    Given how much the JVM has become important in the enterprise, something like Scala makes a perfect fit for a Java replacement. And those people who have used Scala generally say it preserves the spirit of 'TIMTOWDI' while staying good at strong typing, OO and functional paradigms.

    Languages never really drop dead! But they slowly drift into getting irrelevant by the day.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1047371]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (2)
As of 2023-03-20 21:19 GMT
Find Nodes?
    Voting Booth?
    Which type of climate do you prefer to live in?

    Results (59 votes). Check out past polls.