How would you feel if Common Lisps suddenly started sporting infix operator notation? Haskel's alien, counter-intuitive evaluation strategy was actually marketed (circa 2010) as a powerful performance-enhancer that…
> you can just start writing in a declarative style and not worry about debugging, because everything is checked by the type system That is dangerously close to the infamous "if it compiles, then it works" boast, which…
I will never, ever use Haskell in production because of its default evaluation strategy, the wrongness of which was tacitly conceded not long ago with the addition of the strictness pragma (which only works per-module)…
> ... I am a bit lost Google "cognitive dissonance" and the "sunk cost fallacy."
How would you feel if Common Lisps suddenly started sporting infix operator notation? Haskel's alien, counter-intuitive evaluation strategy was actually marketed (circa 2010) as a powerful performance-enhancer that…
> you can just start writing in a declarative style and not worry about debugging, because everything is checked by the type system That is dangerously close to the infamous "if it compiles, then it works" boast, which…
I will never, ever use Haskell in production because of its default evaluation strategy, the wrongness of which was tacitly conceded not long ago with the addition of the strictness pragma (which only works per-module)…
> ... I am a bit lost Google "cognitive dissonance" and the "sunk cost fallacy."