Introducing Haskell to a Company

Re:Introducing Haskell to a Company by incadenza on Tuesday October 02, 2018 @09:24PM (#18126998)

If I'm a manager, and somebody tells me that the development team wont be productive for months, I'd likely ask for some real metric indicating that Haskell solves / eliminates classes of bugs untouched by other statically typed language.

At least some figure indicating that a Haskell app is less prone to bugs, etc.

Otherwise why not throw Typescript at it?

[ Parent | on HN ]

Re:Introducing Haskell to a Company by thedataangel on Tuesday October 02, 2018 @11:41PM (#18127472)

I'd probably rephrase "not" to "less". Haskell is sufficiently unlike other languages that a lot of knowledge/skills that are usually transferable between languages don't apply to it. That means you need to (re-)learn how to solve those problems in Haskell if you want to use it.

The end result is _usually_ better (e.g. Lenses are in almost all cases an improvement over getters and setters; Functors, Monads and Traversable are an improvement over imperative control flow), but damn it it doesn't take a while to get your head around those concepts.

[ Parent | on HN ]

Re:Introducing Haskell to a Company by incadenza on Wednesday October 03, 2018 @02:13PM (#18133046)

yeah it sounds like it. One day I’ll actually dive in and learn that stuff.

[ Parent | on HN ]

Re:Introducing Haskell to a Company by thesz on Tuesday October 02, 2018 @09:44PM (#18127071)

The "not productive for months" is a exaggeration.

Even non-trivial type-level programming can be picked up by complete novice in Haskell in less than month. I experimented with that.

[ Parent | on HN ]