5 ms·
Systems work is the only good reason I've heard not to use Haskell but it's not a good reason for not having learned Haskell. I've heard from people that learn
by coolsunglasses 12y ago
Systems work is the only good reason I've heard not to use Haskell but it's not a good reason for not having learned Haskell.
I've heard from people that learned Haskell independently or went through my guide alike that benefited greatly from having learned Haskell despite not using it at work.
Types are a more compact and faithful representation of code semantics than what most non-Haskell programmers are working with internally. Haskell also teaches you, beyond thinking in terms of types (heh), how to identify patterns & abstractions that most languages wouldn't allow you to credibly leverage.
- coldtea 12y ago>I've heard from people that learned Haskell independently or went through my guide alike that benefited greatly from having learned Haskell despite not using it at work. Could also be a failure to admit they wasted their time, because of sunk costs et al. Not meaning it as snark -- it can always be a valid hypothesis when we're talking about people.
- coolsunglasses 12y agoNo, I know what you mean and I've run into that. I take people don't use/write Haskell regularly and claim to understand it less seriously for this reason. But people that I think got something out of it seem to be benefiting. One is a startup CTO that was using Clojure before - he's ship-of-theseus'ing his way out.
- dllthomas 12y agoI've been using Haskell "at work" on my side projects (which involve other people and a live website, not just toying around), and I'd say that having learned it has impacted the C that I write in my day job. I wouldn't say I'd wasted the time, with or without an impact on my C code.