37 ms·

I've worked at multiple Haskell shops. They've all had problems. None of the problems were actually attributable to Haskell..but Haskell was an easy target for

I've worked at multiple Haskell shops. They've all had problems. None of the problems were actually attributable to Haskell..but Haskell was an easy target for blame by management. I'd say that's Haskell's biggest problem in a professional setting. I know Haskell and Go about equally. Meaning I know all the language features & common libs & have a grip on their runtimes. Go on day 1 was way easier to write and understand than Haskell on day 1. Now that I've normalized their learning curves, Go didn't get much easier to work with. Haskell did - I use my brain way less when writing Haskell than when writing Go. But even then, Haskell or Go. It's all just the same stuff. I've pretty much given up talking on the Internet to people about Haskell. Arguing against some of the pts in this thread about how Haskell isn't good for production. I'll continue to write Haskell for pay for the foreseeable future. If I'm lucky, I'll do it the rest of my career. I don't see any reason why not.

proc0 7y ago
> ..but Haskell was an easy target for blame by management. I'd say that's Haskell's biggest problem in a professional setting. I would say that's a software company's biggest problem instead. I really don't understand how someone with little or no coding experience can be in a leadership position with other programmers who are supposed to be problem solvers and have all the details of how to build something. The bigger the gap in knowledge, the more communication breaks down and the hierarchical structure becomes useless.
- whateveracct 7y ago
  > someone with little or no coding experience can be in a leadership position I had one where the leader in question had coding experience but didn't know Haskell at all. Despite this [1], they tried to read some code (that the Haskellers has no issues with) and couldn't, so he deemed the codebase unreadable and eventually called for a rewrite. Worse, during the debate about the rewrite, there was constant discussion about how the code was unreadable and bad, but it was never sourced to this leader. Instead it was asserted with weasel words only. [1] Maybe it was because of this..this leader was driven by confidence in their experience and seniority.
bojo 7y ago
This comment pretty much sums up my own experience, including learning Go, then Haskell, and the final takeaway - have pretty much given up talking on the internet about Haskell.

proc0 7y ago

> ..but Haskell was an easy target for blame by management. I'd say that's Haskell's biggest problem in a professional setting. I would say that's a software company's biggest problem instead. I really don't understand how someone with little or no coding experience can be in a leadership position with other programmers who are supposed to be problem solvers and have all the details of how to build something. The bigger the gap in knowledge, the more communication breaks down and the hierarchical structure becomes useless.

whateveracct 7y ago
> someone with little or no coding experience can be in a leadership position I had one where the leader in question had coding experience but didn't know Haskell at all. Despite this [1], they tried to read some code (that the Haskellers has no issues with) and couldn't, so he deemed the codebase unreadable and eventually called for a rewrite. Worse, during the debate about the rewrite, there was constant discussion about how the code was unreadable and bad, but it was never sourced to this leader. Instead it was asserted with weasel words only. [1] Maybe it was because of this..this leader was driven by confidence in their experience and seniority.

bojo 7y ago

This comment pretty much sums up my own experience, including learning Go, then Haskell, and the final takeaway - have pretty much given up talking on the internet about Haskell.