although I tried the collaborative features I unfortunately cannot say that I used these extensively for now. Although I found them quite nice, well integrated, seamless, and straightforward!
The issue is again people, they don't wanna change their _archaic_ workflow, stuck with inefficient -copy/paste- loop to the chat (ie. Slack) and back.
The story in the article went a bit too far that I agree, but I guess that is their north-star vision. Current implementation allows you to "join" a workspace session shared by someone, edit the same or different file, follow/watch a certain person, as well as have a chat (without requiring copy-paste) about certain piece of code. (both written or via voice)
If something, large enterprises generally don't support smaller and ambiguous licenses. Therefore, if Zed will allow enterprise licensing (ie. via on-prem license server or volume ordering, SSO, whatever) that would increase their adoption quite well...
For the record: I have never used the collaboration aspects of Zed
What I also have not used is vim emulation, though I have a vim background
As mentioned elsewhere, Zed is still very configuration-dependent to get the full power of it, and a lot of its functionality is never discovered for that reason
What pushed me to try it was Ollama integration which is not an afterthought, then I realized I loved it _way_ more than SublimeText, especially on performance, at first, then everything else once that won me over
I have ~10 running instances at any given moment, and >99% of the time never feel any lag, whatsoever
Another unexpected benefit is that terminals, code editor panels, and assistant chats, get to be sized and fit wherever you want, so it is also kind of a window manager... I often have more terminals open in Zed than in the Window Manager of the OS itself
wouldn’t be the first time a massive investment from someone like sequoia sparks the death of a previously great tool/service
Yea, this announcement makes it less likely I will try Zed
I don't want chat with coworkers in my IDE, nor do I feel the pains they describe with conversations spread between tools. It's not a top 5 problem
although I tried the collaborative features I unfortunately cannot say that I used these extensively for now. Although I found them quite nice, well integrated, seamless, and straightforward!
The issue is again people, they don't wanna change their _archaic_ workflow, stuck with inefficient -copy/paste- loop to the chat (ie. Slack) and back.
The story in the article went a bit too far that I agree, but I guess that is their north-star vision. Current implementation allows you to "join" a workspace session shared by someone, edit the same or different file, follow/watch a certain person, as well as have a chat (without requiring copy-paste) about certain piece of code. (both written or via voice)
If something, large enterprises generally don't support smaller and ambiguous licenses. Therefore, if Zed will allow enterprise licensing (ie. via on-prem license server or volume ordering, SSO, whatever) that would increase their adoption quite well...
For the record: I have never used the collaboration aspects of Zed
What I also have not used is vim emulation, though I have a vim background
As mentioned elsewhere, Zed is still very configuration-dependent to get the full power of it, and a lot of its functionality is never discovered for that reason
What pushed me to try it was Ollama integration which is not an afterthought, then I realized I loved it _way_ more than SublimeText, especially on performance, at first, then everything else once that won me over
I have ~10 running instances at any given moment, and >99% of the time never feel any lag, whatsoever
Another unexpected benefit is that terminals, code editor panels, and assistant chats, get to be sized and fit wherever you want, so it is also kind of a window manager... I often have more terminals open in Zed than in the Window Manager of the OS itself
4 replies →
That's true. Sequoia is often a death sentence for power users. And a huge gamble for the founders
If you're using it at work, the company might decide the risks are outweighed by the increased productivity.