Reflecting on Haskell in 2017

Re:Reflecting on Haskell in 2017 by swyx on Monday December 04, 2017 @11:14PM (#15849669)

hello! i worked there for 2 years. yes it is a fork called Mu, no it is not not lazy. The Mu Core team are devout Haskellers so don't be too quick to dismiss them as abandoning Haskell's core values.

[ Parent | on HN ]

Re:Reflecting on Haskell in 2017 by danpalmer on Wednesday December 06, 2017 @08:46AM (#15860983)

Thanks for the clarification! I never thought they were not devout Haskellers, but I do always wonder about projects that fork a more standard thing for internal use ending up as poorly maintained legacy software.

[ Parent | on HN ]

Re:Reflecting on Haskell in 2017 by tome on Wednesday December 06, 2017 @11:43AM (#15862504)

They didn't fork GHC. They wrote a new Haskell compiler to target a pre-existing runtime that existed inside the bank. For various reasons related to the runtime that meant the language had to be strict. Mu's creation was, in fact, a step away from legacy.

[ Parent | on HN ]