3 ms·
As a fellow emigrant of `Scala is the best island` forced off for pragmatic reasons. I've been around scala long enough to see the rise and fall of multiple ex
by benjaminjackman 8y ago
As a fellow emigrant of `Scala is the best island` forced off for pragmatic reasons.
I've been around scala long enough to see the rise and fall of multiple expeditions into the bowels of the OSGI eclipse cave of horrors (Sean McDirmid / Miles Sabin etc). Before switching horses and settling in Intellij for several years. So I understand where you are coming from.
I've since jumped ship again to vscode (along with typescript), and in my humble experience / opinion, vscode & it's language server protocol (LSP), alleviates quite a bit of this. It abstracts away a lot of common operations from a language to the languages compiler, while providing a consistent front-end. I think if scala eagerly adopts supporting this it would be a good thing. Having a language server protocol applies back-pressure in a certain sense on language features, if you are going to add them, then the tooling (and LSP) needs to support them.
- acjohnson55 8y agoNot sure if you read it in the article, but Scala 3 will have LSP support (if it doesn't already).
- eeperson 8y agoIt already has support although it is not complete: http://dotty.epfl.ch/docs/usage/ide-support.html http://dotty.epfl.ch/docs/usage/ide-support.html
- ionforce 8y agoCould you expand on what this all is? I'm not familiar with what benefits an LSP provides. What is the world like before and after LSP support?
- Joeri 8y agoIt moves code completion and refactoring into a dedicated process behind the LSP API, which is maintained by the language devs. As a consequence the IDE automatically keeps up with language changes.