2 ms·
It would seem that for people reasons Haskell isn't a good choice. However I would say that right now, for people reasons, Haskell is one of the best choices yo
by boothead 11y ago
It would seem that for people reasons Haskell isn't a good choice. However I would say that right now, for people reasons, Haskell is one of the best choices you could make.
Haskell is a very good flag for the kinds of people that make good programmers:
* It's hard to learn.
* Chances of getting a job are minimal, therefore people learn it mostly for their own self edification, and have the kind of grit that keeps them studying for a year or two with not external reward.
* Learning Haskell teaches you some fundamentals that aren't readily discoverable elsewhere.
No one is hiring Haskellers right now, so what you have is a pool of very able programmers, who would love to do Haskell (in fact many would love the chance to use Haskell so much that they'd take a pay cut to do so) and very few people offering them what they want.
If you're a start up, you want to hire a stellar team (possibly at a bit of a discount) and your domain is a good fit then you should seriously consider hiring some Haskellers and letting them write Haskell.
- begriffs 11y agoAt Wagon we use Haskell as our main language. And we are hiring. :) http://www.wagonhq.com/jobs/haskell-engineer http://www.wagonhq.com/jobs/haskell-engineer
- boothead 11y agoI would guess that you'd corroborate my characterization of hiring Haskellers as an embarrassment of riches then? :-)
- swsieber 11y agoMy thinking is sort of along the same vein: you can train people, you can't "train" a language. And if you can't train the person, why did you hire them? The cost of training is much like the cost of evaluating frameworks and tools and choosing the best ones (with the huge caveat that you invested in a person, and they can leave... but if their strongest suite is the obscure language, it puts a damper on things...)