http://qs321.pair.com?node_id=1047108


in reply to regarding intolerance to perl which I observe

I'm in the process of changing jobs. I'm currently working at a huge company (~60.000 employees) and here I'm working in Python. I don't think Python is a bad language, but some things it feels a bit weird and I actually prefer Perl. So now I'm joining a startup (not that small, about 80 people) and there I'll be working in Perl. In this startup Perl is used for test automation, where I think it's a really strong language.

So this is just a personal anecdote that there are still startups out there that start using Perl. And from my previous experience (moving from a Perl background to a Python job) I really wouldn't be afraid of sticking with Perl. The switch to another language isn't that hard (if you have to do it at some point because your new job requires it) and all companies I interviewed with never saw this as a problem.

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

Replies are listed 'Best First'.
Re^2: regarding intolerance to perl which I observe
by fisher (Priest) on Jul 31, 2013 at 12:19 UTC
    there are still startups out there that start using Perl.

    Sounds funny enough.

    I heard about clojure startups, and scala startups, and even Go language startups, but perl? Hm.

    Thank you, you gave me an illustration that I need =)
[reply]

      My last two jobs were at Perl/JS startups.

      Perl is one of the best choices for a start-up because it's amazingly fast for for prototyping, it covers so much ground, and is such good glue.

      During the years we worked on Viaweb I read a lot of job descriptions. A new competitor seemed to emerge out of the woodwork every month or so. [I would look] at their job listings. After a couple years of this I could tell which companies to worry about and which not to. The more of an IT flavor the job descriptions had, the less dangerous the company was. The safest kind were the ones that wanted Oracle experience. You never had to worry about those. You were also safe if they said they wanted C++ or Java developers. If they wanted Perl or Python programmers, that would be a bit frightening-- that's starting to sound like a company where the technical side, at least, is run by real hackers... –Beating the Averages

      (update: fixed bracket HTML.)

[reply]

        That note from Paul Graham, is not about using 'Perl' in specific. He seems to be trying to point out the fact that technically oriented people, will tend to use the current set of non-mainstream technologies against the current enterprise trends even if they are relatively new. If you apply that line of thinking. Python/Perl are the new C++/Java of our times. C++/Java have graduated to COBOL level ancientness by now.

        Yes, Perl is still awesome. But the world now takes many things we offer for granted, Because nearly every half decent language these days has those features. The situation is not like what it was 20 years back. We have some marginal advantages over other languages, in the exact same way they have some other advantages over us. But its not like what it was 20 years back, where Perl was the only alternative available.

        The situation with many other languages like Python is no different. And they too losing users to languages like Go and Scala. But just like how CGI, gave Perl some breathing time. So will Django and Rails give Python and Ruby some breathing time.

        We have nothing radically new to offer for years now. There is incremental development. But that is that. This is really the reason why Perl 6 is all the more so important for Perl.

[reply]

In Section Meditations