Let's open another thread... > > > Could that also be > > > addressed by eating our own dog food and running the LSP on the target > > > VM? > > > > That is an unexplored area for me. I assume it is a long road to get there > > and keep the current level of Java support. > > Almost certainly. OTOH there seems to be a lot more focus on LSP at > the moment, so I wondered whether it's a useful direction of travel > that actually focuses efforts and longer-term reduces workload? Just > throwing it out there - I like the idea of decoupling into UI and > headless processes anyway, potentially running on different VMs. A > thread for another day!
Looks like the invention of LSP was really great move by the VSCode guys! It allows each language to provide good enough IDE support by coding in the language itself and writing the "server side" IDE piece while reusing internals of own language compiler. No surprise everyone is providing LSP servers. > I remember > talking with you at JCrete on this during early transition, and about > the fact that the other, other VSCode LSP support was using it. The days where NetBeans could afford to support any language on the planet are over. There is just a few of us and we don't have the momentum we used to have in the first ten years of this century. In such situation re-using work done by others via LSP is the best option we have. It took me a long time to convince Jan Lahoda to bet on LSP, but the results are great! I am really enjoying editing TypeScript in NetBeans these days and that's all possible only because of yet adopting LSP and creating infrastructure to use such servers. From the other side (again thanks to Jan's early work) we can use the NetBeans infrastructure and expose it (via LSP) to VSCode users. As VSCode support is important for OracleLabs strategy, it actually means quite a lot of contributions from Sváťa, Dušan, Martin, me. As there is close synergy between VSNetBeans and real NetBeans, the whole project benefits. All of that has only been possible thanks to relying on LSP. Amazing result, I'd say. -jt > I > don't think it still is, maybe it could be encouraged back to it - an > independent component that provides useful features for editors in > general, and is consumed by other projects, is a good thing IMO! PS: Such an independent component would have to be built on top of `(nb)- javac`. I don't understand how that would simplify the licensing or distribution? As far as I can tell all the problems we are solving now would remain the same. PPS: Running `ant -f java/java.lsp.server/ build-lsp-server` actually creates such component. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
