We Have to Start Over: From Atom to Zed
11–20 of 243 posts
Re: We Have to Start Over: From Atom to Zed
#12Had a look at the About page, and the live coding feature does sound useful. I'm sure the guys are excited; it's a fun project. You get to write algorithms, optimise performance, and do GPU programming. But who needs another text editor that will probably never reach feature parity with Vim and a terminal multiplexer.
Re: We Have to Start Over: From Atom to Zed
#13Had a look at the About page, and the live coding feature does sound useful. I'm sure the guys are excited; it's a fun project. You get to write algorithms, optimise performance, and do GPU programming. But who needs another text editor that will probably never reach feature parity with Vim and a terminal multiplexer.
zed is actually very fast though
Re: We Have to Start Over: From Atom to Zed
#14[flagged]
Re: We Have to Start Over: From Atom to Zed
#15Love how much thought is being put into what you “gold-plate”. I’ve always felt that my best work comes around on round two (or three or four…).
Curious what you are planning for the ability to script the configuration? I haven’t played with zed much yet; is it possible today? Would something like Neon [1] help bridge the gap from VSCode and old Atom users?
Re: We Have to Start Over: From Atom to Zed
#16Re: We Have to Start Over: From Atom to Zed
#17Re: We Have to Start Over: From Atom to Zed
#18Re: We Have to Start Over: From Atom to Zed
#19SIMD I wonder if Zed uses SIMD, to read in text from a file or write out text to the display. Mitchell recently wrote about how he got a massive reduction in latency, by implementing SIMD in his terminal app (which is analogist to an editor) https://mitchellh.com/writing/ghostty-devlog-006 https://hachyderm.io/@mitchellh/111919642467789362