I use Haskell in my daytime job (web based SaaS) and we have “solved” our needs in different ways. However, today I got curious on how the Haskell Foundation (HF) sees different parts of the ecosystem and if HF has blessed/affiliated/sponsored any of them.
In this post I do not argue that HF should officially aid different actors nor which - I’m just curious on the current situation. I have checked the HF website and other sources and found some answers but not the full picture.
I know what I like and what I think is a good way forward but that is not the point of this post - I am looking for an update on the official HF standing so far.
So my question is this:
- Which categories below, if any, have “official”/blessed/affiliated/sponsored/“standard” options? I mean primarily from a HF standpoint since HF tries to facilitate and coordinate the community long term.
- Do any categories have options that are “deprecated” or recommended to avoid?
I include some options in brackets, not to suggest that those should be the official choice but to clarify what I mean. It could be that no option in that category should be backed by HF.
- Download and installation (ghcup)
- User guide
- Documentation (haddock)
- Linting (hlint)
- Formatting (ormolu)
- IDE-tools (Haskell Language server)
- Testing (Hspec, Hedgehog)
- Database (Persistent, rel8)
- Web page framework (IHP, yesod)
- Api framework (servant)
- Build tools, (cabal,stack, nix,
- How to build in a modern CI setup, building naïvely from scratch takes too long
- APM integration, Application Performance monitoring (New Relic, Instana)
- Deploy method(Docker, nix, aws elastic beanstalk, Azure)
If this is clearly documented somewhere and I’ve missed it I’m sorry.
Have a great day!