3 ms·
I think a lot of these people go to Haskell direct from scripting language backgrounds, and thus have little experience of static type systems before that. You
by repolfx 7y ago
I think a lot of these people go to Haskell direct from scripting language backgrounds, and thus have little experience of static type systems before that. You can see the same thing with Go: it's very apparent a lot of programmers praising how productive and consistent it makes their codebase are comparing it to something like Python or JavaScript.
In fact the top answer says:
Look, I have a lot of experience using Haskell. I understand how often code doesn’t really work after it typechecks. I never say “it typechecks so it works” with a completely straight face. But I also have a lot of experience with Python and JavaScript.
So these comments aren't really about Haskell in my view. People would get the same feel from lots of languages with decent type systems if they came from a scripting language background. I often find my code works first time in Kotlin, and the times when it doesn't only rarely things that a more sophisticated type system would have caught.