For me personally, settings UI isn’t needed at all — I prefer configs, I can search (text or keys), use outline, comments, navigation & editing history, VCS features, etc…
All extensions should be built by hand currently, and unfortunately any LS must be wrapped in adapter-extension like it is in Zed — that’s terrible thing and in Zed it is so just because vendor wants to control anything about what and how you use with the editor. I’ve worked on wrapper-less LS(P) & DAP support (like it is in Helix) for Gram, but currently I’m stuck and freeze it for some time. But you can try too!
It definitely has a lot of promise! I’d say it’s not quite where I would switch from VS Code, but I’d imagine with not a lot of work, it would be there. 8/10 will recommend.
First impressions: not bad, but a little buggy.
I can’t edit the settings in the settings UI and there’s no indication why.
The language servers all say they’re broken, but they all seem to be working fine.
It’s incredibly fast. Way faster than my current VS Code setup.
It’s minimal, and I like that.
(Running on macOS.)
For me personally, settings UI isn’t needed at all — I prefer configs, I can search (text or keys), use outline, comments, navigation & editing history, VCS features, etc…
All extensions should be built by hand currently, and unfortunately any LS must be wrapped in adapter-extension like it is in Zed — that’s terrible thing and in Zed it is so just because vendor wants to control anything about what and how you use with the editor. I’ve worked on wrapper-less LS(P) & DAP support (like it is in Helix) for Gram, but currently I’m stuck and freeze it for some time. But you can try too!
It definitely has a lot of promise! I’d say it’s not quite where I would switch from VS Code, but I’d imagine with not a lot of work, it would be there. 8/10 will recommend.