3 ms·
If the enterprise wanted as much compile time checking as possible, why haven't they adopted something like Haskell years ago? The checks done by the type syste
by Eiwatah4 13y ago
If the enterprise wanted as much compile time checking as possible, why haven't they adopted something like Haskell years ago? The checks done by the type systems of the JVM and CLR are laughable in comparison. There must be some different reasons at play here, too.
- hvs 13y agoOf course there are reasons beyond compile-time checking, that is just one of the many requirements of an "enterprise" language. Haskell has strong type checking but fails in many other areas. Namely, being easy to understand by mediocre to average developers (and even some good developers).
- lmm 13y agoThey're getting there. The leading edge of enterprise is already using scala or F#, which have a lot of the power of Haskell (in fact I'd argue scala's is more powerful in some ways, e.g. typeclasses cease to be a special case). In terms of using Haskell in the enterprise, it isn't standardized enough (most libraries rely on GHC extensions), the library ecosystem isn't mature enough, cabal is still a mess (it's too easy to get your dependency tree into a broken state), there's not enough commercial support, there's not enough deployment/monitoring infrastructure around. Fundamentally, it was produced by academics who didn't care about selling it to the enterprise, and the effort to address these concerns hasn't entirely happened yet. It's getting there, and I think we'll see more of it as time goes on.