Introducing Haskell to a Company
I like haskell. It reads like a math proof more than a cooking recipe. very elegant. I&#x27;m a math guy and i&#x27;d love to get back to it in my free time.<p>But i don&#x27;t think i could recommend it for the enterprise. not honestly. I tried to do a professional project in Haskell once. it was a good fit, since it was about parsing and generating configuration. However I was still new to it. the bottom line: it&#x27;s just not that great for newbies. since most people are going to be newbies at it, i could not recommend it at all. sometimes i think the language even goes over my head, and I&#x27;m supposed to be a pretty smart cookie.<p>OP makes &#x27;they are not going to be productive for months&#x27; sound like an obstacle to overcome. But if I tell management the honest story in advance and they will obviously not give me the greenlight.<p>But i suppose it is a language that&#x27;s a reasonably easy sell to management if you hype up the reliability stemming from the type system and skip over the downsides. managers dont know much about programming, but they hate incidents even more than developers. if you are honest, you have to tell them that in practise operational problems become more likely. I mean: ever tried to install ghc on a centos server behind a firewall?<p>If i have to recommend something now it would be python. because it&#x27;s easy and because i started using it for my personal stuff. i know lots of languages and that&#x27;s what i end up coming back to if i need to do stuff quickly.<p>OP doesn&#x27;t even mention the real advantage to introducing Haskell. Few colleagues will end up being good at this, so if a piece of critical software is written in Haskell and you are the only one who is a great Haskell engineer, it increases your negotiating power in the company. people won&#x27;t be able to get around you and it will be hard to deny a request for increased compensation.