News for hackers. Stuff that matters.
Re:The Mid-Career Crisis of the Perl Programmer by natch on Monday March 10, 2014 @11:14AM (#7373358)
Every programmer who loves Perl should ask him/herself: Is this a case of Stockholm Syndrome?

I think for me it was. The jobs kept coming, stuff kept getting done, I enjoyed myself, I'm proud of most of the code I wrote, and yet, it never felt completely right. Probably because Perl has always been more of a petri dish for idioms than an organized home for them.

Re:The Mid-Career Crisis of the Perl Programmer by mattfenwick on Monday March 10, 2014 @11:31AM (#7373469)
I think you made an interesting point, but IMHO it should be generalized:

> Every programmer who loves Perl should ask him/herself

I think this should read "Every programmer who loves any technology should ask him/herself [...]". Asking this question may be a great way to learn more deeply about the technology. I don't think that Perl is special in this regard.

> Is this a case of Stockholm Syndrome?

Not if the programmer acknowledges there's problems with Perl, but loves it anyway; not if the programmer has experience with other technologies that have different strengths and weaknesses.

Re:The Mid-Career Crisis of the Perl Programmer by roeme on Monday March 10, 2014 @11:29AM (#7373457)
Stockholm Syndrome implies that Perl is bad, no?

I disagree. Just as it allows you to write horrible stuff, you can just as well get your shit together and do it maintainable, robust and nice to the eye :)

And as the author states, you (almost) always have an choice to run other languages, where perl runs. Not really a hostage situation, methinks.

Edit: Not that I particularly like Perl, but neither do I hate it. I think it's somewhat bad reputation stems more from the fact, as described above, that it forces you less to do things nicely and is very accessible to the, let's say, less experiences programmers - so a lot of quickly cobbled together stuff flies around.

Re:The Mid-Career Crisis of the Perl Programmer by lazyjones on Monday March 10, 2014 @11:40AM (#7373533)
> it allows you to write horrible stuff, you can just as well get your shit together and do it maintainable

Many years of programming practice and SE theory have taught some of us that discipline is not the main concern of most programmers and the higher a level you require of it, the more you will be disappointed. Which means that you tend to get more maintainable results from languages which either require very little discipline to produce good code or those that strictly enforce discipline (e.g. Go).

Sadly, even the code on CPAN (which was built to withstand some scrutiny apparently, or why else would anyone release it to the public) is often so badly written that I wouldn't want to debug or maintain it.

> And as the author states, you (almost) always have an choice to run other languages, where perl runs. Not really a hostage situation, methinks.

In practice you're more likely to find old, hard to maintain Perl code bases that noone is able or wants to rewrite in another language, if you get hired to program in Perl. If there was a realistic choice to use another language, it was likely made already years ago.

Re:The Mid-Career Crisis of the Perl Programmer by roeme on Monday March 10, 2014 @05:52PM (#7375928)
> In practice you're more likely to find old, hard to maintain Perl code bases that noone is able or wants to rewrite in another language, if you get hired to program in Perl. If there was a realistic choice to use another language, it was likely made already years ago.

Having worked in several corporations now I have to respectfully disagree. My experience is that either the code base was scheduled to be retired (but we all know how that usually turns out: the app is used for at least 3x(abs($retiredate - $now)) + $rand ), nobody could be bothered to keep the system current, or there was always something more important to do (which overlaps a bit with the second point).

Come to think of it, I really can't come up with a situation where you can't replace perl with a reasonable amount of work? But then again, I'm not active in the perl field.

Re:The Mid-Career Crisis of the Perl Programmer by AdrianRossouw on Monday March 10, 2014 @12:22PM (#7373814)
I fell off my chair when I installed R for the first time, and I discovered that I needed a FORTRAN interpreter.

Apparently the math libraries written in fortran back in the day have become such a foundational part of analytics, that nobody really wants to re-implement them.

Re:The Mid-Career Crisis of the Perl Programmer by alephnil on Monday March 10, 2014 @12:58PM (#7374089)
That is not really the reason. The reason is mainly BLAS, that implements some of the most commonly used linear algebra operations (matrix multiplication, matrix solvers, singular value decompositions etc). This is implemented in optimized versions for almost every CPU available. BLAS is written in FORTRAN, but it is not true that it has not been reimplemented. In fact CPU vendors frequently reimplement it tailor made for their CPU.

On the other hand, the API is not something that is subject to change. A lot of software expect this to be stable, like Matlab, R, Octave, Numpy, and a lot of others.

Re:The Mid-Career Crisis of the Perl Programmer by baldfat on Monday March 10, 2014 @12:34PM (#7373914)
FORTRAN is an amazing language for some very specific jobs and is still a great tool for a specific job. It's fast does scientific and numerical calculations incredibly fast.

I haven't touched Fortran in 20 years though :) I loved me Pascal except the semi-colon key broke on my keyboards.

Re:The Mid-Career Crisis of the Perl Programmer by Solarsail on Monday March 10, 2014 @07:34PM (#7376422)
Picking a(n extremely small) nit (with a fine tooth comb):

Fortran compiler. There are no Fortran interpreters in existence, anywhere, that I've been able to find. For FORTRAN 70, Fortran 90, or any other versions. If someone manages to find an interpreter and proves me wrong, I'd love to hear about it.

Re:The Mid-Career Crisis of the Perl Programmer by AdrianRossouw on Monday March 10, 2014 @08:28PM (#7376669)
thanks. i actually went back and forth between compiler and interpreter and didn't think to look it up.

That'll show me to rely on my hazy memory of something I read five years ago on wikipedia =)

Re:The Mid-Career Crisis of the Perl Programmer by alephnil on Tuesday March 11, 2014 @10:37AM (#7379395)
It should also be mentioned that when people use Fortran, it is usually because they need the fastest numerical processing available. An interpreter would usually not meet that need. With JIT compilers embedded in interpreters, the difference is blurred, since the result is machine code, unlike traditional bytecode interpreters, that usually are an order of magnitude slower than compiled code.

That said, I'm also not aware of any Fortran interpreters, and it would surprise me if there is one.

Re:The Mid-Career Crisis of the Perl Programmer by steveklabnik on Monday March 10, 2014 @03:24PM (#7375117)
My vague understanding is that Fortran can actually be faster than C in certain numerical calculations because the language doesn't make the same kinds of guarantees. And therefore, Fortran will live forever.
Re:The Mid-Career Crisis of the Perl Programmer by chromatic on Monday March 10, 2014 @07:23PM (#7376373)
Fortran disallows pointer aliasing and it has some language intrinsics which operate on arrays as a whole, so the compiler can emit processor-specific SIMD instructions. I'm sure that a very clever programmer could use restrict and inline assembly in C to get similar benefits, but you know as well as I do that having the language make these guarantees for you is helpful.
Re:The Mid-Career Crisis of the Perl Programmer by BugBrother on Monday March 10, 2014 @04:36PM (#7375533)
I posted this the last time I saw you making ~ the same point https://news.ycombinator.com/item?id=7316490

(And yeah, 10+ years old Perl code bases might be less than pretty... The environment evolves quickly, for good and bad.)

Re:The Mid-Career Crisis of the Perl Programmer by sliverstorm on Monday March 10, 2014 @11:35AM (#7373499)
The jobs kept coming, stuff kept getting done, I enjoyed myself, I'm proud of most of the code I wrote

Please excuse me for being an idiot, but I don't see the problem.

Re:The Mid-Career Crisis of the Perl Programmer by ionforce on Monday March 10, 2014 @11:53AM (#7373621)
It's a perception problem.

Just because something is locally good doesn't mean there isn't a more optimal good elsewhere.

Re:The Mid-Career Crisis of the Perl Programmer by smacktoward on Monday March 10, 2014 @12:31PM (#7373896)
But thinking like that creates what I'll call the Walter Mitty Problem: making a great living, enjoying a loving family, great health, etc., but being unable to take satisfaction from any of that because you're too busy dreaming of being a larger-than-life figure. The better your circumstances get, the more dreaming of even better ones becomes a game of diminishing returns.

(For those of you who only know Walter Mitty from the Ben Stiller movie, here's the original short story: http://www.newyorker.com/archive/1939/03/18/390318fi_fiction...)

Re:The Mid-Career Crisis of the Perl Programmer by untog on Monday March 10, 2014 @12:23PM (#7373828)
Short term-ism vs. Long term-ism.
Re:The Mid-Career Crisis of the Perl Programmer by ttflee on Thursday March 13, 2014 @07:15AM (#7391083)
'But this long run is a misleading guide to current affairs. In the long run we are all dead.'
Re:The Mid-Career Crisis of the Perl Programmer by pekk on Monday March 10, 2014 @01:22PM (#7374275)
Stockholm syndrome isn't the same as being in a stable, mutually beneficial marriage to someone who's not completely compatible with you.
Re:The Mid-Career Crisis of the Perl Programmer by tommu on Monday March 10, 2014 @07:33PM (#7376417)
Is post industrial work ever completely compatible with the essential human condition?