language-server-protocol

LSP support is planned! Although, the rationale for including it is for advanced language features, like "go to method". I'd be surprised if other editors were using it for syntax highlighting. I've had to jump through hoops to keep that performant on large files. Seems like putting that in a separate process would make performance even more of a challenge. I found this after a quick search: https://github.com/Microsoft/language-server-protocol/issues...

Very good points. Just to add a few more details on the LSP and VS Code side of things: - VS Code implements syntax-aware code folding using the LSP. This means that folding is super flexible but it is also makes computing folds fairly expensive. And every time the document changes, the language server has to re-compute and update the folds. In almost all cases, language servers is just generating folds based on the document's syntax anyways. Tree-sitter is interesting because it lets folding and other syntax based language features be calculated accurately and quickly on the client, freeing up the language server to do more interesting things (or just go to sleep for a moment). Document outlines are similar; VS Code uses the LSP for this but in many cases the same syntax derived outline could be generated by tree-sitter. - The LSP probab

Sourcegraph CEO here. Microsoft designed and released LSP. We are eternally grateful for that! We played no part in its creation. The first LSP mention links to the repo at https://github.com/Microsoft/language-server-protocol with more info. We have, however, built and/or sponsored many language servers. (Those, in turn, build on compiler APIs that other people tirelessly created, to which we also owe thanks.)

Why don't all this projects have a singular protocol for writing plugins, this way evreyone can benefit from something. just like all the IDEs are starting to support microsoft's language server protocol: https://microsoft.github.io/language-server-protocol/specifi... https://github.com/Microsoft/language-server-protocol

Jetbrains products used to be superior. Better refactoring and speed than Eclipse or Atom. However the sale might be a consequence of the fact that free and nearly equally powerful alternatives such as VSCode are competing directly with Jetbrains products to become the developer's preferred editor. With the rise of Microsoft's free Language Server [1] I'm wondering how long it takes until open source IDEs will be on par with Jetbrains. [1] https://github.com/Microsoft/language-server-protocol

The protocol itself is open source: https://github.com/Microsoft/language-server-protocol . I'm sure the folks in charge of it would be happy to talk to PyCharm if they wanted to contribute.

Moving language parsing/refactoring/etc into a separate daemon is a step towards unifying tooling around specific protocols for interacting with compilers. Microsoft's effort towards a single language server protocol is worth mentioning: https://github.com/Microsoft/language-server-protocol I'd love to see a future when new languages/compilers can implement this protocol for their external compiling daemons and just get support in all the various text editors/IDEs automatically.