acme-lsp VS plan9port

They use acme-lsp btw.

vim/nvim are still heavy beasts.

Here's a recent example which made me laugh: 2 months ago, a "shortcut" for reverse search was implemented in acme[0], a 30 years old text-editor. It's not even qualified as a "feature" yet, rather, as an "experiment"[1].

Every little decision is carefully weighted; every square inch of the software is carefully and precisely designed. Japanese wooden planes are similarly designed: they don't look like much, especially in comparison with more modern, shinier tools, but they're surprisingly well-thought.

[0]: https://en.wikipedia.org/wiki/Acme_(text_editor)

[1]: https://github.com/9fans/plan9port/commit/0c79c32675e83ff3d8...

Acme is genuinely worth trying, you can run it on Linux/Mac without a VM [1]. I'm pretty sure Russ Cox [2] and Rob Pike use it as their daily driver which is insane because it doesn't even have syntax highlighting. I used it for years when I was in school as an exercise in masochism, but I learned a lot about Unix, and the mouse-driven workflow actually grew on me.

[1]: https://9fans.github.io/plan9port/

[2] https://9fans.github.io/plan9port/

If you find it too complicated and closely tied to Go internals, you can also check out Plan 9 from User Space's version, which is itself based on libthread from Plan 9 starting from 3rd edition, which is itself based on Alef's implementation of channels (Alef is Go's grandfather).

I tried plan9port's mk for a moment out of curiosity. I quickly ran into an annoying usability problem: it compares file mtimes with second accuracy.

https://github.com/9fans/plan9port/blob/cc4571fec67407652b03...

With sub-second build times for individual targets, this causes mk to needlessly recompile files because the target may have the same mtime as the prerequisites.