3 ms·
Things are slowly improving. For example you now have the Haskell Language Server (https://github.com/haskell/haskell-language-server https://github.com/haskell
by dgellow 6y ago
Things are slowly improving. For example you now have the Haskell Language Server (https://github.com/haskell/haskell-language-server https://github.com/haskell/haskell-language-server) which makes it way simpler to integrate haskell into your editor.
I'm using VSCode and the official extension (https://github.com/haskell/vscode-haskell https://github.com/haskell/vscode-haskell). The default experience is not at the level of what I have with Go or Typescript but already quite good (though it's not that stable IMHO, I have to restart the server more than I would like).
The Haskell Platform (https://www.haskell.org/platform/ https://www.haskell.org/platform/) makes it simple to install almost everything you need to get started (the compiler, standard libraries, build tools, etc).
It's not there yet, the beginner dev experience is still painful and frustrating, but things improved quite a lot.
- macspoofing 6y agoI understand the point and I wasn't criticizing Haskell because it isn't just Haskell that has this problem. It was a general observation from my own personal experience working with Haxe, Erlang, and Dart. The tooling for all was mediocre at best in the early days, and all of them gotten better (I lost track of Haxe and Erlang a few years back), but my general observation is that it really isn't enough to come up with a nice language (and all of them were/are nice languages). After the compiler and runtime, the community has to have a laser focus on tooling and bootstrapping because that will be a huge factor in whether the language increases in popularity or not. And we see examples of this all over the place. For example, Rails (and Ruby) become as popular as solely because they were so easy to setup.
- dgellow 6y agoYes, 100% this.