{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreihghln7holtp6ad7yi6s6kiioimeryl7tvikbe5aeyoehhmes25g4",
"uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mhsrj5rr5ev2"
},
"path": "/t/flexible-haskell-a-new-plugin-for-jetbrains-ides/13813?page=2#post_37",
"publishedAt": "2026-03-24T06:51:46.000Z",
"site": "https://discourse.haskell.org",
"tags": [
"https://plugins.jetbrains.com/plugin/24123-haskell-lsp",
"“Cursive” plugin",
"Editing and Navigating C++ Code",
"Working with the Call Hierarchy - JetBrains Guide"
],
"textContent": "Congrats on the release.\n\nHow does your plugin compare to this one in practice: https://plugins.jetbrains.com/plugin/24123-haskell-lsp? I understand it could work “better” for bigger projects given hls is known to be rather slow?\n\nI intend to try it myself but, since I don’t work with Haskell daily/professionally, I’ll have to find a good project and time slot to got give it a fair assessment.\n\nSide note, I can’t help but think about Clojure’s “Cursive” plugin which has got a different monetizing strategy from you, offering free non-commercial licences “in good faith” (renewable every 6 months), which I’ve always appreciated because I have never invested in the Clojure language itself, but still could get a “full user experience”. If I ever get into this language, I would gladly pay for a personal licence given the plugin is that good, I’m all for paying to get better tooling personally… Maybe something to think about? I don’t know if the plugin author would say it was a winning move though.\n\nGetting back to your plugin, do you support the “call hierarchy view”?\n\n * Editing and Navigating C++ Code\n * Working with the Call Hierarchy - JetBrains Guide\n\n\n\nThis feature _is_ available in the vscode plugin FYI, but not the jetbrains plugin I’ve linked above. As far as I understand, it can be implemented via LSP calls, but possibly in a more performant way via the psi tree?",
"title": "Flexible Haskell - a new plugin for JetBrains IDEs"
}