4 ms·
If you're asking people to learn Haskell in order to find out which kinds of programs it's better on, that's a tough ask in a universe that has dozens of langua
by AnimalMuppet 5y ago
If you're asking people to learn Haskell in order to find out which kinds of programs it's better on, that's a tough ask in a universe that has dozens of languages that one could learn. Most people aren't going to bite on that. No, tell us what kinds of problems it's good for, and if we care about those kinds of problems, then we'll consider Haskell.
- the_af 5y ago> No, tell us what kinds of problems it's good for, and if we care about those kinds of problems, then we'll consider Haskell. Haskell is good for writing general purpose code in the Functional Programming style [1]. It's not the only language that supports this style, but it's one of the most opinionated about keeping to this style that is also general-purpose, pragmatic, and has some industry adoption [2]. You can also see read what wiki.haskell.org has to say [3]. [1] "Why Functional Programming Matters": https://www.cs.kent.ac.uk/people/staff/dat/miranda/whyfp90.pdf https://www.cs.kent.ac.uk/people/staff/dat/miranda/whyfp90.p... [2] Commercial Haskell: https://github.com/commercialhaskell/commercialhaskell#readme https://github.com/commercialhaskell/commercialhaskell#readm... [3] "Why use Haskell": https://wiki.haskell.org/Introduction#Why_use_Haskell.3F https://wiki.haskell.org/Introduction#Why_use_Haskell.3F > If you're asking people to learn Haskell in order to find out which kinds of programs it's better on I'm not asking people to do anything, but if they do want to understand the tradeoffs of any technology, sometimes the only way is the hard way: learning it. I find all too often what people really want to know is a quick and easy glance at how much language X differs from something they already know (usually C derivatives, or Java, or Javascript, or Python).
- spekcular 5y agoAgain, I find this answer somewhat evasive. Many languages support functional programming and are used commercially. You still have not told us: What problems is Haskell best for? What is its comparative advantage? I don't think it's unreasonable to expect a more concrete reply to that quesiton than "First master the language, then figure it out."
- the_af 5y ago> You still have not told us: What problems is Haskell best for? Let me be honest here and say I don't find your tone helpful. "You still haven't told us" makes you sound as if you're in a group, critiquing from the tribune. This isn't helpful for honest conversations. There's no "us", there's just you, and I don't owe you any explanation. That said, I provided plenty of links in my answer above, which address at least some of your questions. Have you read them? The site https://www.haskell.org https://www.haskell.org has plenty of testimonials that you could also read to figure why some shops and people have chosen Haskell. Maybe you could send Simon Peyton Jones an email, he's one of the friendliest guys in the software industry. I don't think I've ever read or heard him say anything dismissive about any other person or technology.
- spekcular 5y agoI'm sorry, I don't want to be adversarial or dismissive. It's just that I've been asking a very specific and precise question, and you keep replying to the question but do not answer it. This is a little frustrating!
- the_af 5y agoBut I did answer it, more than once and with links you can read! What I cannot do: provide you with a single sentence stating why you should use Haskell. I don't think anyone can. For the record, I found your single sentence about Rust totally unconvincing as well; I do find Rust compelling because of tutorials, long articles I read about it, and a workshop I once did with a Rust practitioner. None of this is equivalent to debating/convincing on HN. (Similarly, I find Go not compelling because I had to use it for my day job and everything about it made me chafe). So my advice to you: read the links I provided, and keep in mind they are just a starting point. Do a workshop. Work on a midsize problem, maybe also write some Advent of Code Haskell solutions. Or not. It's ok to just go with your gut feeling and focus on Rust. There's a finite amount of time you have available for exploring technologies. Rust will serve you well.
- 5y ago