With Haskell, one always finds articles explaining how great it is, how its features (pure functionality) lend to correct code. But, articles explaining the core use cases and how only this language enabled solving it are rare. I'd love to read someone's decision postmortem that goes something like 'Here is a problem we were looking to solve. And here is how specific features A/B/C of Haskell helped us solve it well.…
Is Haskell really the language of geniuses and academia? (2019)
21–30 of 83 posts
Re: Is Haskell really the language of geniuses and academia? (2019)
#22With Haskell, one always finds articles explaining how great it is, how its features (pure functionality) lend to correct code. But, articles explaining the core use cases and how only this language enabled solving it are rare. I'd love to read someone's decision postmortem that goes something like 'Here is a problem we were looking to solve. And here is how specific features A/B/C of Haskell helped us solve it well.…
The lesson I derive from Haskell is that "If it compiles, it will work"
1. is inflated nonsense
2. has a lot less to do with Haskell-the-language than with Haskell-the-type-system
I have observed a similar phenomenon with Rust. That statement is not perfect, it's hyperbole. If it compiles, it doesn't mean it will run (otherwise, why bother writing code? We just write function signatures and call it a day).
But Rust's type system is incredibly sophisticated, just like Haskell's.
And guess what... Rust supports mutability. It doesn't just support it, it encourages it. It tells you "Step over that fence, it's okay, I got your back".
It's so liberating.
The secret here is not functional programming. It's not immutability.
It's a sound and powerful type system.
Re: Is Haskell really the language of geniuses and academia? (2019)
#23With Haskell, one always finds articles explaining how great it is, how its features (pure functionality) lend to correct code. But, articles explaining the core use cases and how only this language enabled solving it are rare. I'd love to read someone's decision postmortem that goes something like 'Here is a problem we were looking to solve. And here is how specific features A/B/C of Haskell helped us solve it well.…
And everywhere else, unfortunately.
Go is an overreaction in the opposite direction. In 2010 I can't agree that there is a good reason to make a language without generics and reasonable error handling from the very start.
Re: Is Haskell really the language of geniuses and academia? (2019)
#24Earlier quoted context omitted.
It sounds like you folks didn't give the language enough of a chance and may have felt the friction of trying to write Haskell in the style of another language. It takes a while to learn how to go with the grain, in any language. While I totally sympathize with this, I'm not sure it's a very good vantage point from which to judge a language.
Which goes back to the root comment and the issue it raised: Where are the practical Haskell tutorials. No preaching, no "you're holding it wrong", ONLY this: "you need to handle arbitrarily nested JSON? here's how".
- Simple Haskell Handbook[1]
- Haskell (Almost) Standard Libraries[2]
- [0]: https://lhbg-book.link
Re: Is Haskell really the language of geniuses and academia? (2019)
#25Earlier quoted context omitted.
It sounds like you folks didn't give the language enough of a chance and may have felt the friction of trying to write Haskell in the style of another language. It takes a while to learn how to go with the grain, in any language. While I totally sympathize with this, I'm not sure it's a very good vantage point from which to judge a language.
Which goes back to the root comment and the issue it raised: Where are the practical Haskell tutorials. No preaching, no "you're holding it wrong", ONLY this: "you need to handle arbitrarily nested JSON? here's how".
Learning an entirely new language is hard and requires patience and perseverance!
Re: Is Haskell really the language of geniuses and academia? (2019)
#26With Haskell, one always finds articles explaining how great it is, how its features (pure functionality) lend to correct code. But, articles explaining the core use cases and how only this language enabled solving it are rare. I'd love to read someone's decision postmortem that goes something like 'Here is a problem we were looking to solve. And here is how specific features A/B/C of Haskell helped us solve it well.…
Re: Is Haskell really the language of geniuses and academia? (2019)
#27I’ve found this explanation to be useful and easy: Haskell is the Mercedes of programming languages. It has features you didn’t know you wanted or needed and eventually other languages will get there, and Haskell will seem average/harder to differentiate. I’ve written a more practical post on why Haskell is worth using[0], excuse the clickbait title. [0]: https://vadosware.io/post/how-and-why-haskell-is-better/
Re: Is Haskell really the language of geniuses and academia? (2019)
#28With Haskell, one always finds articles explaining how great it is, how its features (pure functionality) lend to correct code. But, articles explaining the core use cases and how only this language enabled solving it are rare. I'd love to read someone's decision postmortem that goes something like 'Here is a problem we were looking to solve. And here is how specific features A/B/C of Haskell helped us solve it well.…
>But, articles explaining the core use cases and how only this language enabled solving it are rare From my (limited) experience with Haskell, my impression is that it's strongest in domains that map _very_ well to formal mathematical models. Mathematical computation is an obvious example, but things like programming language parsers are also really intuitive to build in Haskell. My experience trying to use Haskell f…
Re: Is Haskell really the language of geniuses and academia? (2019)
#29I’ve found this explanation to be useful and easy: Haskell is the Mercedes of programming languages. It has features you didn’t know you wanted or needed and eventually other languages will get there, and Haskell will seem average/harder to differentiate. I’ve written a more practical post on why Haskell is worth using[0], excuse the clickbait title. [0]: https://vadosware.io/post/how-and-why-haskell-is-better/
There’s a reason Toyotas sell like hotcakes. It gets you from A-to-B reliably.
Most SWE's brains can't afford more though, sadly.
Re: Is Haskell really the language of geniuses and academia? (2019)
#30Same thing seems to apply to monads. Haskell programmers use them a lot but other languages seem to work just fine without them.
So my guess is that many of the special features of Haskell are solutions to problems you will have if you insist that language is lazy and pure.