{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicdolkxal35xvzmidnysxy3jdetwlzxwnxvsg7z62oa6hqf3535uq",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mhddtot5cse2"
  },
  "path": "/t/flexible-haskell-a-new-plugin-for-jetbrains-ides/13813#post_5",
  "publishedAt": "2026-03-18T10:43:40.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "Glad you asked. First of all, it is a JetBrains IDE extension. There are many developers out there who prefer the JetBrains IDEs over VSCode (myself included) - for various reasons. It is not a competition, though, I personally think that more tools = better. Haskell should be on any IDE available, if you ask me and this just expands it to IntelliJ, PyCharm, GoLang etc…\n\nThen there is the grammar itself. VSCode traditionally relies on TextMate grammars, which are regex-based. There is an alternative with Treesitter, but I am not sure if the vscode plugin uses that. That means the editor’s own understanding of your files is pretty much flat without the language server running. Ours is based on a BNF structure, which gives us an actual hierarchy. Things like auto-complete, on-hover documentation, validation, refactoring all come naturally because the underlying structure is already there. With VSCode you really depend on the language server for all of that, whereas for us HLS is just an addon on top (we do support using it, but do not rely on it). And once indexed, navigation and lookups are fast because the IDE indexes elements on the fly via its own PSI tree, independent of any external server.\n\nAnyway, in terms of features, out of the box it should make it super easy for everyone to work with. There are still things left to improve (which is why i really want feedback - did I mention that?). But I think it makes an interesting addition. Give it a go",
  "title": "Flexible Haskell - a new plugin for JetBrains IDEs"
}