From that same paragraph:
> That said, there are ways of dealing with this in languages like Python, they're just a little more verbose and you don't get the compiler checking that you've exhaustively handled all cases, for example. It won’t compile, it won’t accept that idea.
> [Haskell is much more bullet-proof than] IF NATALPLANET == “MARS”
And perhaps there might be something like a Python Enum HOWTO
I'm not familiar with Python, but if those are traditional enums and not sum types then you're missing out on a lot in terms of domain modelling.
And yet missing less than the OP's
IF NATALPLANET == “MARS"Comparing to Python and Javascript, referencing an unused name in source without reaching it in your execution path will not cause an error.
a=4
3+a
3+a or 3+b
in a strongly-typed language, that would break compilation. So, Java and C will not compile those, either, but the article doesn't go into other cases where Haskell types are more useful for preventing various errors, such as Data.Result, which can either be a result of the type you expect or an error type, and which the compiler requires you to handle both cases. I think the write up would have benefited from some of the more advanced cases like this.
"Increased abstraction means that you can write things much quicker and more simply than in another language."
Except for any other kind of higher level language.
> [Haskell is much more bullet-proof than] IF NATALPLANET == “MARS”
As is any other non-stringly-typed language, so everything other than Tcl. And even Tcl is misunderstood, it's actually pretty awesome for its intended purpose. And of course you can write stringly typed code in Haskell just as much as you can in any other language.
and so on.