News for hackers. Stuff that matters.
Re:A man, a Plan. No canals (2011) by pjmlp on Wednesday January 09, 2013 @10:41AM (#5032009)
- Parenthesis

- Lack of a proper IDE

- The AI Winter

- Mainstream hardware wasn't powerful enough

- Most blue collar developers don't understand FP concepts

Just some possible reasons out of my head.

Re:A man, a Plan. No canals (2011) by ccdan on Thursday January 10, 2013 @08:40PM (#5040884)
"- Most blue collar developers don't understand FP concepts"

HAHAHA! The vast majority of FP advocates are either unemployed or work as math teachers. Like it or hate it, FP is absolutely nothing more than a pseudo-programming paradigm (largely emulating some concepts from astract math and using notation somewhat similar to math notation) that attracts people who can't wrap their heads around OOP, rich frameworks and other associated stuff. Sorry folks, computers are neither abstract nor stateless. And the same holds true for software, which often deals with real world stuff, which again, is neither abstract nor stateless. Virtually everything that can be done in a functional language, can also be done in a procedural or OOP language. The opposite on the other hand is totally untrue. It's really funny to see how FP advocates struggle even with some extremely basic things. Using languages/platforms like C/C++, Java,.Net - there's always an increase in performance compared to any functional language (yeah, including scala, f#, clojure ocaml an so on) The "elegant code" argument is one of the most ridiculous things FP advocated come with, since it's almost always synonymous with crappy, cryptic code that no one wants to read besides its authors (maybe not even them after a few weeks or months) :D So I'm afraid that the FP advocates are far worse than real blue collar workers.

Re:A man, a Plan. No canals (2011) by martinced on Friday January 11, 2013 @10:07AM (#5042937)
"Sorry folks, computers are neither abstract nor stateless."

It's true. But you know what computers are first and foremost? They're deterministic.

And you know what's one the biggest problem programmers do face in the Real-World [TM] when the shit hits the fan (and most devs' jobs is to fix shit that just hit the fan)? It's being able to recreate the state and to then be able to deterministically reproduce the shit that did hit the fan. As to prevent it from hitting the fan again.

Why do we seen market makers using 90 Ocaml programmers and raving about it?

Why do we see investment banks moving from Java to Clojure and slashing their codebase by doing so by a factor of ten? And then explaining how easier their life became in the face of changing requirements (eg new laws/regulations coming in)?

Do you really think that a codebase ten times smaller is "harder to read"? Do you really think that making it easier to reproduce the state is not a goal worthy to achieve?

I realize you feel insecure in your Java/C# + ORM + XML + SQL hell but don't worry: there's always going to be lots of real-world jobs for code monkeys like you ; )

Re:A man, a Plan. No canals (2011) by ccdan on Friday January 11, 2013 @03:34PM (#5044830)
"It's true. But you know what computers are first and foremost? They're deterministic."

That's like saying that computers have mass and are made of matter.

"And you know what's one the biggest problem programmers do face in the Real-World [TM] when the shit hits the fan (and most devs' jobs is to fix shit that just hit the fan)? It's being able to recreate the state and to then be able to deterministically reproduce the shit that did hit the fan. As to prevent it from hitting the fan again."

That's false. Programmers don't have to recreate the same exact state, actually it's not necessary to recreate the error at all in many cases. There are more tools than you can imagine for identifying errors from logging to memory dumpers and analyzers/profilers...

"Why do we seen market makers using 90 Ocaml programmers and raving about it? Why do we see investment banks moving from Java to Clojure and slashing their codebase by doing so by a factor of ten?"

Well, I'm afraid that happens in your imagination only. I also happen to be a trader. Almost NO ONE uses functional languages (fewer than 0.01 %) for financial trading. The main languages are C/C++ (especially for high frequency trading) and, of course, Java and also .Net.

"I realize you feel insecure in your Java/C# + ORM + XML + SQL hell but don't worry: there's always going to be lots of real-world jobs for code monkeys like you ; )"

You're pretty delusional about how secure or insecure I feel (haha!) and how much of a "codemonkey" I am. LOL! You don't even know me, but you already pretend that you know me. Unfortunately for you(and all those like you), this is a typical characteristic of FP advocates: you live in an illusory world, have a totally distorted view about software engineering and of course about the people who do make real world software. Anyway, it's always funny to see the reactions of FP advocates when they're left without any objective, verifiable, real-world arguments. :D

Re:A man, a Plan. No canals (2011) by wmil on Wednesday January 09, 2013 @11:46PM (#5035481)
- The fact that most tutorials cover topics like "rolling your own object system" before topics like "writing a string to a file".

Lisp example also always cheat at things like Quines... the program will return itself instead of writing itself to stdout.

Re:A man, a Plan. No canals (2011) by TylerE on Wednesday January 09, 2013 @11:30AM (#5032295)
Another I'd add is lack of a clear execution model.

There is something to be said for being able to just run 'python foo.py'

Where as in many lisp variants there is no clear entry point, and often not really an "interpreter".

Re:A man, a Plan. No canals (2011) by andyjohnson0 on Wednesday January 09, 2013 @11:27AM (#5032275)
Interesting. I didn't realise that I'm a 'blue collar' developer. What do I need to do to upgrade to white collar?
Re:A man, a Plan. No canals (2011) by rafcavallaro on Wednesday January 09, 2013 @11:36AM (#5032326)
Your parent implies that not getting functional programming concepts makes one a "blue collar" (i.e., less sophisticated, more commodity) programmer. Presumably, understanding functional programming is one necessary requirement of upgrading to "white collar" (i.e., more sophisticated, less replaceable) programmer.
Re:A man, a Plan. No canals (2011) by wtracy on Wednesday January 09, 2013 @01:35PM (#5032641)
I'm guessing he's implying that "white collar" programmers have a degree in Computer Science that is heavy in theory (as opposed to being primarily vocational, like, say, the University of Phoenix). Most such curricula will include at least one class that focuses on functional programming. (UC Berkeley teaches their 101 CS class using Scheme!)

The people who care about this distinction are the sort of people who give job interviews where they ask you to implement a balanced binary search tree on the whiteboard and then grill you on the order of growth of each function that you wrote. :-)

Re:A man, a Plan. No canals (2011) by pjmlp on Wednesday January 09, 2013 @03:11PM (#5033208)
"Blue collar" is a common expression to describe developers without CS background, that usually develop CRUD applications and are expected to be easily replaced by management.
Re:A man, a Plan. No canals (2011) by minimax on Wednesday January 09, 2013 @11:46AM (#5032374)
"What do I need to do to upgrade to white collar?"

Develop a stubborn willingness to ignore the at-times unsatisfactory performance of immutable data structures.