News for hackers. Stuff that matters.

A comment on Escape IntelliJ: Scala and Kotlin LSPs on Emacs Eglot. Parent comment

Re:Escape IntelliJ: Scala and Kotlin LSPs on Emacs Eglot by mechanicum on Thursday July 23, 2026 @09:05AM (#49020945)
My understanding was the biggest issue has always been that javac is a poor foundation for any kind of live tooling like LSPs?

It’s less “make me a Java LSP” than “rewrite javac around incremental compilation and exposing a semantic DB”. Which sounds like a much harder problem.

[ Parent | on HN ]
Re:Escape IntelliJ: Scala and Kotlin LSPs on Emacs Eglot by marginalia_nu on Thursday July 23, 2026 @09:18AM (#49021129)
We have a java compiler API nowadays that solves this.
[ Parent | on HN ]
Re:Escape IntelliJ: Scala and Kotlin LSPs on Emacs Eglot by mechanicum on Thursday July 23, 2026 @10:22AM (#49022108)
It looks like that was added in Java SE 6, and doesn’t materially change the underlying problem. Have there been more recent developments?
[ Parent | on HN ]
Re:Escape IntelliJ: Scala and Kotlin LSPs on Emacs Eglot by marginalia_nu on Thursday July 23, 2026 @12:05PM (#49023875)
I was thinking of JEP 484, which I guess technically isn't a compiler API as much as it is a class file API, but that's kind of a big deal for this type of work as probably the primary work the parts of the classpath you currently aren't editing, moreso than parsing a single .java-file, and the kludges we had before this API (e.g. ASM) were incredibly fragile.
[ Parent | on HN ]