Re:Why Maybe Is Better Than Null
by cantankerous on Friday April 19, 2013 @02:58PM
(#5578148)
True. I think it's also a covert argument for static type checking, though ;-).
Give me a statically typed Python and a type system that can handle external hardware poking around in its memory and I'm in ;)
I'm sort of a fan of Haskell already, to tell you the truth.
> Give me a statically typed Python
Not sure that's so far from Haskell, really... :-P
> and a type system that can handle external hardware poking around in its memory
Can it be in isolated places? That's doable...
Not sure that's so far from Haskell, really... :-P
Maybe it's my lack of experience talking. Haskell feels heavier in a lot of places. I think the focus on compilation in the backend is almost a downside here, too.
Can it be in isolated places? That's doable...
Depends on the application. There's a lot of hardware out there that does really weird stuff. There's some interesting work in Haskell-space (eg Atom) but I don't know how comprehensively mature it is.
Making types non-Nullable by default is nice, though. Even in a dynamic language you can have a syntactic distinction to make interfaces more explicit.