3 ms·
Most of my limited production Haskell experience has been schlepping enterprise JSON using AWS Lambda and calling REST APIs. I’ve not had any bug reports in ag
by agentultra 6y ago
Most of my limited production Haskell experience has been schlepping enterprise JSON using AWS Lambda and calling REST APIs.
I’ve not had any bug reports in ages. Which is counter to what most of the teams were used to when deploying services in JavaScript or Ruby. Usually you test like hell, QA, ship, get a few error reports from users, fix them, get one or two a couple months later and fix those... then a year later you change something and get a bunch of new error reports about the feature that used to work... and you fix those.
Haskell forced me to address most of those errors before my program would compile. I had to write a few tests but orders of magnitude fewer than I was used to. I shipped fast.
I got one report from the customer many months later when I made a mistake due to a miscommunication of requirements. One test case prevented that kind of error happening again inadvertently and shipped in less than an hour. Haven’t heard any reports since.
Haskell is my go to where I can get away with it. Absolutely solid stuff.
- Tainnor 6y agoI have quite a personal interest in learning more about pure FP, type systems, theorem provers and all the hot stuff. But: you're also comparing Haskell to completely dynamic languages like Ruby or JS. There are things in the middle. Even Java lets you avoid many silly typing errors and if you use something like Kotlin (and you use it well, not just as a slightly more modern Java), you can IMHO get quite far in terms of correctness for typical web backends. Now the power of languages like Haskell may be warranted in more complex scenarios and I don't want to claim there are no benefits to it, but there are degrees in between the madness that is JS and something like Haskell.