Haskell in Production
felixmulder.com
Haskell in Production
1–10 of 242 posts
Re: Haskell in Production
#2This is a great guide and sound advice. And hopefully in a year we'll see the community converge on Polysemy (or fused-effects for performance) to make this strategy even more natural.
Re: Haskell in Production
#3If I remember correctly, Co-Star, the horoscope app, runs Haskell on the backend.
Re: Haskell in Production
#4All the interesting code is in the next post, http://felixmulder.com/writing/2019/10/05/Designing-testable....
I'm not sure why they use a generic monad rather than ST, they don't need continuations for this.
The Reader monad with a big record is standard Haskell, it's basically what GHC uses: https://github.com/ghc/ghc/blob/1219f8e8a3d1b58263bea7682232...
data-has is less standard, it only seems to have been used seriously by one project, which has a bug on file to stop using it: https://github.com/myfreeweb/magicbane/issues/20
But overall it's interesting, we'll see where the series goes.
Re: Haskell in Production
#5If I remember correctly, Co-Star, the horoscope app, runs Haskell on the backend.
Re: Haskell in Production
#6I really wish Java had associated types and static methods as parts of interfaces (i.e. constructors as part of the interface). Those two features make complex architectures much easier to design and use.
Re: Haskell in Production
#7The more I see it in use, the more I want to learn Haskell, but I can't think of a practical reason to do so.
Re: Haskell in Production
#8The more I see it in use, the more I want to learn Haskell, but I can't think of a practical reason to do so.
I think the reason should/could be abstraction. If you find yourself doing kind of the same thing over and over but don't see how you could extract the repetative part in a scalable way in a language with less type support then there may be a good use case for Haskell there.
Re: Haskell in Production
#9> Haskell is great for business and great in production.
Hot take: no it isn't. It is extremely hard to learn, has an extremely confusing + needlessly complicated syntax and I question the payoff immensely. I question the well-being of anybody who subjects themselves to the pain and torture that is Haskell.
If I stood up in a corporate business boardroom meeting for tech analysis on a new project and said "I want to write it in Haskell", I'd get laughed + kicked out.
Re: Haskell in Production
#10Always nice to see Haskell at work. I haven't learned the language myself yet, but I absolutely love postgREST, which is implemented in Haskell.