Hacker News new | ask | show | jobs
by alberth 805 days ago
Additionally, it’s also not yet another “text editor”.

It’s very clear the differentiation of Zed will come in the form of the collaboration functionality it will have.

1 comments

And speed. Startup time is instantaneous, in comparison to VS code say.
The same team that "erased" native editors is now selling us the solution to the problem they created.
Erased? On the contrary it seems, to me at least, like new editor development has really grown over the last few years. Editors like Kakoune, Helix, Micro are coming along nicely. I'm looking to switch, at least partially, to Helix soon myself.
How much are you going to pay for the 5 seconds per day you open up your editor? Most people dont even close it in the first place.
I haven't tried this software, but I imagine it's more about having the UI keep up, so you can stay in the flow state.
Is raw code output so large that your editor can't "keep up" really something to optimize for? For me personally I write as little code as possible. you don't get bonus points for number of lines you write.
Yes, while at the same time having a responsive UI is important for editing, and we're not hanging less stuff in our editors than yesterday. Both emacs and neovim and vscode are essentially IDEs today.
Yes it is, especially when you work with lots of large files in big codebases. I can open files in Vim that would crash VSCode, which is essentially why I still use Vim for certain parts of development.
Presumably speed is an overall important factor for the creators — not just startup speed — and I'd imagine it translates into speed elsewhere, such as input latency and UI responsiveness.
Straight up not true. Running my local copy it takes 5 seconds for the window to appear.
If this happens with Zed 0.129 or later, could you open an issue? We had a problem at one point where there was a delay in macOS verifying our app’s code signature because we weren’t attaching the code signature correctly.
5 seconds sounds extremely long for a macOS native application. Could be macOS security (XProtect), storage latency?, tons of compressed memory?...