Hacker News Reader

Comment by unshavedyak | Hacker News Reader

Has JetBrains ever discussed putting out some sort of generic LSP oriented product(s)?

I own a couple JetBrains product for very select things but as much as i enjoy the company i will never use them for my actual code.. because i'm a 20 year addict of Terminal based editors (currently on Helix).

I'd love to see the considerable effort they put towards tooling available to the Terminal oriented audiences. Yea, probably small audience.. but i just often see this stuff and think "What if this was an LSP? I'd purchase it in a heartbeat!"

Especially since multi-LSP editing is apparently viable. Eg Helix supports multiple LSPs for a single context, now. Though i'm not clear on the specifics yet, as i've not tried it yet.

I really want to give them more money. I just don't want to use their UIs for my code.

View on HN

Their Fleet IDE is exactly that. It’s in development right now, but a public beta is available: https://www.jetbrains.com/fleet/

Edit: I just realized you meant the opposite, where the IDE is just a language server. Fleet is an IDE that uses language servers

I don't know if the sort of deep refactoring and other integrations they offer in their IDEs would be possible in the LSP protocol as it exists today. I believe debuggers for vscode have a similar DAP protocol. Any way, my point is, they have something great that works well for their users, so it doesn't seem like a very large market to make a less powerful version for a small set of new users. I also suspect that the sort of developers who don't use their IDEs but instead use an LSP based editor that is free/open-source would be unlikely to _pay_ for Jetbrains LSP based offering, however high quality/unique it might be.

How might a Language Server Protocol (LSP) work for debugging? And predictive debugging in particular? Any examples you've seen? Do LSPs have a mechanism by which debugging could work? (I haven't researched this yet.)

Note: I ask the above questions in an attempt to move the conversation towards predictive debugging. Like many, I visited this thread because I'm interested in the core topic: debugging. We're probably not here for a general discussion about the pros and cons of JetBrains / non open-source software / IDEs.

The LSP version of debuggers is essentially DAP, and it is gaining some support: https://microsoft.github.io/debug-adapter-protocol/

Like LSP it's a bit crippled compared to a normal debugger, but the universally-pluggable aspect is compelling.

Thanks for sharing. I can see why are you excited about this. For others who might not click through:

> What is the Debug Adapter Protocol?

> Adding a debugger for a new language to an IDE or editor is not only a significant effort, but it is also frustrating that this effort can not be easily amortized over multiple development tools, as each tool uses different APIs for implementing the same feature.

> The idea behind the Debug Adapter Protocol (DAP) is to abstract the way how the debugging support of development tools communicates with debuggers or runtimes into a protocol. Since it is unrealistic to assume that existing debuggers or runtimes adopt this protocol any time soon, we rather assume that an intermediary component - a so called Debug Adapter - adapts an existing debugger or runtime to the Debug Adapter Protocol.

Hello, I am an LSP bot designed to help clarify human language interaction. The above commenter used the term LSP without defining it. LSP means "Language Server Protocol." ~ Your friendly neighborhood Hacker News LSP Bot

Reply on news.ycombinator.com