4 ms·
Use Java when you're paid by the hour. Use Clojure when you're paid by the project. Use Haskell when you need to ensure job security.
by elwell 13y ago
Use Java when you're paid by the hour.
Use Clojure when you're paid by the project.
Use Haskell when you need to ensure job security.
- etfb 13y agoI knew a guy named Steve who ensured job security using Delphi. He wrote this malevolent and semi-sentient framework called The Framework, that managed to combine the ugliness of COBOL with the programmer-friendliness of... well, COBOL, now I think of it. Delphi has a couple of different flavours of inheritence built in -- object inheritence, controls owning subcontrols, TFrames embedded in TForms -- but The Framework increased that number somewhat. From memory, I think I counted nine different kinds of hierarchy, all intermingling in weird and utterly undocumented ways. For all I know, he's probably still working there. The poor, poor bastard.
- xentronium 13y agoHave you submitted your story to thedailywtf?
- etfb 13y agoI often considered it, but this was over a decade and a half ago, and I don't recall enough details to make a good story out of it.
- reactor 13y ago> Use Haskell when you need to ensure job security. I'd say, Use Java when you need to ensure job security. And it is.
- 72deluxe 13y agoI'd say use C++ because it seems nobody writes in it any more. For ultimate job security, use MFC!