3 ms·
> Don't compare. Just use. Take it at face value. Figure out what becomes easy, what becomes hard. Isn't this precisely what the author did? The bad parts he m
by majewsky 10y ago
> Don't compare. Just use. Take it at face value. Figure out what becomes easy, what becomes hard.
Isn't this precisely what the author did? The bad parts he mentioned were mostly "this is stuff that the compiler could've catched, but it didn't and thus gave me a hard time".
If we were going to carry out this argument, it would probably just boil down to the familiar debate of how strict a type system should be. The author is just a proponent of expressive type systems, and he plainly puts it in the title: "a Haskeller's perspective".