‹ BackHN Continuity

Thread

Why building a Rust LSP is hard

144 points · 77 comments · agluszak

  1. qudat · · focus · HN ↗
    Tangentially, since I now write a lot of Zig and there’s no official LSP, I decided to see what life would be without an LSP for all my projects (Go, TS, Python).

    Honestly, my LSP requirements are minimal: go to def, find all references, and symbol search. I’ve been wanting to try ctags for awhile and finally made the switch.

    Another consideration were all the posts about how grep is better than LSPs for LLMs.

    It really pushed me to just get better at grep. There have been a ton of benefits: I can symbol search outside of my editor, it’s much faster than an LSP, minimal configuration. It feels more like a universal tool I can use instead of a tool for IDEs.

    1. wredcoll · · focus · HN ↗
      It's faster than an lsp?? What on earth are you doing? Even just the context switch to typing the right grep command is slower than ctrl-g or whatever.
      1. qudat · · focus · HN ↗
        LSP load times can be brutal (or crash entirely) and I have a shortcut to grep the word under the cursor.

        Ctags is a symbol indexing system so I run it once for a project and can do symbol searches in my editor or using fzf.

        I have ctags index the languages stdlib as well which is really handy for quick symbol searching -> open my editor to read more

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.