ema VS haskell-language-server

You can baptize yourself by either moving a sufficiently complex Haskell codebase to Nix or building a website using something like Ema (with full Nix+Flakes support!)

Also, I'm willing to mentor anyone who is interested in improving Ema or Emanote.

Clarification: Emanote is a successor to Neuron, and written on top of Ema.

I maintain an extended version of Emanote in Haskell (as an Ema app) that does custom stuff like visualize my hledger transactions, track time, generate invoice and provide custom views of my Markdown notebook, like a Twitter-like timeline generated from H2 headings (with date) from across notes.

The advent of language server protocol made possible the creation of HLS (Haskell Language Server), and there are plugins for many editors, such as vscode-haskell, that allow you to have auto-complete, auto-import, and automatic function signatures—also available to your editor of choice. The whole feedback loop of editing, compiling, and running is greatly improved.

HLS 2.3.0.0 is currently broken on Windows.

The Haskell community has been focusing on tooling and IDE support in the last several years. Haskell-Language-Server is a huge improvment, so the experience is probably much better than you remember, but it'll still be a while before it catches up with Rust.

static-ls is a low memory language server for Haskell that serves as an alternative to (hls)[https://github.com/haskell/haskell-language-server] with less functionality by using statically generated information. It is intended for (Highly recommend hls instead if you aren't having these issues):

I think the corresponding HLS PR is https://github.com/haskell/haskell-language-server/pull/3462, so it isn't landed yet but hopefully can be part of a HLS release before too long. (I'm not sure if it will make it in to the very next release because we're due one out to support GHC 9.6.1 pretty soon.)