One thing I worry about a little is the business model. They want to target teams and charge for the cooperative features. But as a single user I’d love a way to just buy a lifetime license and feel that I can expect at least five years of use. I don’t like when software I love treats me like a casual fling.
Thanks in advance! Looks cool
Edit: signed up for the waiting list and received "Zed currently only targets macOS" so sounds like they only target ~10% of the actual market. Interesting strategy.
It’s likely quicker to develop for a single OS and then build the additional UIs with a more feature-complete app.
The Xi editor team quickly found out how much of a mess "native" gui's were on windows. Zed will hopefully add support for vulkan and linux/windows later, but it makes sense to start off on macOS
What's the state of art open source editor/extension/protocol/whatever that enables two or more persons work on the same open files in real time? Something better than the ssh access which forces one person to work at time, then save, then the other person reloads.
Can this made to work with a GUI editor? Like neovide or emacs but in X11/wayland not tty
Is there some inherent difficulty is this, or is it just "there is no standard" -> "nobody implements one"?
- zed.dev has crdt's/collaborative editing as one of its selling points, but they're planning to offer this collaboration as part a paid service to businesses. - vscode has its own sycronous collaboration plugin, but its proprietary and they declined to release the source code or offer to port it to other editors - you could probably build a plugin that bridges emacs and neovim, but it might be a bit slow as you'd have to "translate" the buffer from one editor to the other
There is an inherent difficulty in implementing it, getting asycronous collaborative editing right is hard. Combine that with how few people on emacs/neovim actually use collaborative editing (emacs still has a mailing list and does code via patches) and the chance for a "universal" version is practically nil.