[dnsco]

It's not just tree-sitter that makes zed feel snappy.

If you're using a reasonably fast language-server, which rust-analyzer apparently is (I didn't know this using vscode), the autocomplete & intentions feel instantaneous.

I think the team has learned a lot from previous editor implementations (they were the core team of atom that was notoriously slow), and so they've had an opportunity to do a lot of stuff right.

FWIW they also are the team that originally wrote tree-sitter.

The quickness feels more like it's in the core of the editor. I was shocked how much it impacted the editing experience when I tried it in early beta.

[FridgeSeal]

> If you're using a reasonably fast language-server, which rust-analyzer apparently is (I didn't know this using vscode)

Some more anecdata to back this up: initial workspace load in VScode I can watch RA tick through its progress. Clean and boot up Zed and the same process is so fast that it’s almost unbelievable.

[widdershins]

I've been impressed with the C++ clangd language server snappiness in Zed compared to both CLion (my old favorite) and Emacs (apple of my eye for 2.5 yrs).

I always thought the major slowness was coming from clangd itself, so I'm surprised and impressed to see that Zed appears to be quicker on this front. I might be using Zed as a 'second opinion' editor because of this.

However, now I'm used to the infinite customizability and coziness of Emacs, it's going to be hard for me to move across to Zed permanently.

[erk__]

Emacs have some issues with LSP speed because of the json parsing not being the fastest which have lead to work like this: https://github.com/blahgeek/emacs-lsp-booster.

[widdershins]

Ah, thanks for the link, I hadn't seen that. I will give Eglot another go with this set up!