# Elm Camp session about editors and IDE plugins

**URL:** <https://discourse.elm-lang.org/t/elm-camp-session-about-editors-and-ide-plugins/9230>\
**Category:** Show and Tell\
**Created:** [July 16, 2023, 5:57pm UTC](https://discourse.elm-lang.org/t/elm-camp-session-about-editors-and-ide-plugins/9230 "2023-07-16T17:57:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lydell](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/lydell/32/178_2.png) [@lydell](https://discourse.elm-lang.org/u/lydell)\
**Post date:** [July 16, 2023, 5:57pm UTC](https://discourse.elm-lang.org/t/elm-camp-session-about-editors-and-ide-plugins/9230/1 "2023-07-16T17:57:24Z")

</div>

We talked about:

- How the [Language Server](https://github.com/elm-tooling/elm-language-server) has made amazing advancements in type inference, but unfortunately is plagued by some **stability issues** due to Tree Sitter (which is a shame since Tree Sitter seems like such a cool, promising technology). The Vendr folks also mentioned how the language server became too slow for their giant code base.

- The newer [Elm Land VSCode extension](https://github.com/elm-land/vscode/), which is pretty **bare bones but super fast and stable** (and handles the Vendr code base). Even with its constraints of being super light and fast, it still has potential for implementing many more features, like finding usages.

- How [intellij-elm](https://github.com/klazuka/intellij-elm/) is **packed with power user features,** but unfortunately is **unmaintained,** which results in fear of it breaking one day, and missed opportunities for more power usage features.

- How the **bleeding edge, super cool [elm-dev](https://github.com/mdgriffith/elm-dev) project** fits in. The cool thing is that elm-dev can already run in server mode and has knowledge of types and usages of all code, and a bunch of other things editor plugins want. And it’s really fast and has the stability of the Elm compiler at its core. There is a **potential future where all editors might be powered by elm-dev.** Note that elm-dev currently does not use the Language Server protocol, but their own server protocol. It seemed like people didn’t fully agree on the spot on the protocol choice. I also got the feeling that elm-dev is a very ambitious project, and it’s **not clear yet** what paths maintainers and contributors want to explore first – people might want to try to pull it in different directions, based on what they’re the most excited about. But it’s early days.

- Several people using **intellij-elm** at work felt like they could make their **companies pay for using the plugin,** so someone could get time to work on it by being paid for it. While [JetBrains products might get Language Server support soon-ish](https://blog.jetbrains.com/webstorm/2023/06/webstorm-2023-2-eap7/), it feels a bit like Language Server support always will be a bit second class, so a separate plugin might still be worth it for the JetBrains products, taking full advantage of all their stuff. Some people expressed how they felt like it would be fun to work on the plugin, but don’t have time.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/elm_lang/original/1X/50a05e53677a2c3b47776d7abd0f113eb50193a1.png) [@system](https://discourse.elm-lang.org/u/system)\
**Post date:** [July 26, 2023, 5:58pm UTC](https://discourse.elm-lang.org/t/elm-camp-session-about-editors-and-ide-plugins/9230/2 "2023-07-26T17:58:22Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.