Hacker News new | ask | show | jobs
by godelski 154 days ago 

  > starting vscode again takes about a second, and then maybe 10s of seconds of background processing
Yet I'm doing the same thing instantly or near instantly.

I don't reboot often and I'm still lazy and will leave projects open often, but honestly, have you considered that your workflow is an adaptation to the wait time?

  > Navigating between files (using fuzzy search or go-to-definition) is just a lot faster and more convenient.
I agree? But why do you think people don't fuzzy search in vim? Or the terminal? There's been tools to do this for a very long time. Fzf is over a decade old and wasn't the first
1 comments
vanviegen 153 days ago
If you're using vim as an IDE (which is if course perfectly doable), then why does it matter if startup time is 50 or 1000 ms. You typically leave them running.

> Yet I'm doing the same thing instantly or near instantly.

Does vim somehow allow LSP servers to index faster? Or are you not actually doing the same thing?

link
godelski 153 days ago
Why are you leaving them running? Because they are slow to load?

Yes, Neovim supports LSP and it is very very fast.

I'm not sure why any of this is surprising. We're talking about the same company who is speeding up their file browser by loading it at boot time rather than actually trying to fix the actual fucking problems. Why is it surprising that everything else they make is slow and bloated as shit (even more as they've shoving AI into everything)

https://neovim.io/doc/user/lsp.html

link
vanviegen 150 days ago
The point of LSP is that neovim is using the same servers for this as vscode. So I guess you work on smaller projects or with languages that have faster (usually meaning less fully featured) LSP servers.
link