I tried out the editor because of this post: it looks very promising. Unfortunately I can't use it because it doesn't have support for remote hosts/devcontiners. That feature of VScode is critical to my workflow, as I don't actually want to program on a Mac host, but rather use my Mac as a portal to the VMs and containers I actually code on. It massively helps with segmentation of my projects and improves my security…
I use development virtual machines to segment projects and clients also although I just run my editor in each VM. What's the benefit of the vscode remote hosts/dev containers over a normal remote session?
We Have to Start Over: From Atom to Zed
81–90 of 243 posts
Re: We Have to Start Over: From Atom to Zed
#82Before anyone jumps on a new text editor band wagon, just a note on the license they have you agree to in using it: "Customer Data consisting of User content created while using the Solution is classified as "User Content". User Content is transmitted from Your environment only if You collaborate with other Zed users by electing to share a project in the Editor. [...]Zed's access to such User Content is limited to de…
Of course if you choose to share your project with others for collaboration, the content of that project is transmitted from your machine, what else would you expect? How would it work otherwise?
Re: We Have to Start Over: From Atom to Zed
#83Had 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.
In my opinion I wish more editors would become a face to Neovim which can run in a headless mode, allowing you to not have to emulate VIM at all, but take full advantage of it and all its plugins. It still kills me JetBrians chooses to maintain what VIM users call an awful plugin that simulates VIM, when they could just implement a Neovim front-end natively into their IDE, giving them the edge of "we fully support Ne…
Re: We Have to Start Over: From Atom to Zed
#84Earlier quoted context omitted.
zed is actually very fast though
This might be one of those things like monitor refresh rate where you can only really tell the difference if you've experienced the better version for a while, but I haven't ever felt slowed down by the speed of VS Code.
Re: We Have to Start Over: From Atom to Zed
#85Earlier quoted context omitted.
This might be one of those things like monitor refresh rate where you can only really tell the difference if you've experienced the better version for a while, but I haven't ever felt slowed down by the speed of VS Code.
it is actually faster and snappier to use on a beefy M2 max, on the same hardware zed starts up in half the time. the difference is very noticeable. of course it is much less configurable and doesn't work with a lot of things VS Code can do easily. edit: see this comment for a much better explanation than mine of what I originally meant https://news.ycombinator.com/item?id=39409763
VS Code starts in under a couple of seconds, and I have it open all day long; once open, other windows open even faster than that.
If it took any longer than a couple of seconds, I'd start blaming the extensions other editors won't have.
Re: We Have to Start Over: From Atom to Zed
#86Re: We Have to Start Over: From Atom to Zed
#87Earlier quoted context omitted.
For our team, VS Code is reaching that point. The Macbooks can’t keep up with VS Code’s decay. Unfortunately Zed lacks good defaults (like a way to change tabs without the mouse) and certain vs code features like snippets. Makes it difficult to transition a team which has been dependent on Vscode and which has absolutely no interest in spending our days configuring tools
Are you running a lot of extensions or giant file sizes or how are the computers not keeping up with VS Code?
Re: We Have to Start Over: From Atom to Zed
#88Great interview! Love 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? [1]: https://github.com/neon-bindings/neon
I went from Atom to Pycharm to Vscode. Both transitions were fairly easy. Though I’ve never had any complex configurations.
Re: We Have to Start Over: From Atom to Zed
#89There was an editor I forgot the name might of been Omnivim, which was coded in ReasonML, but compiled natively to a UI, and supported VS Code plugins, which is still wild to me. Anyway, development kind of died off on it, it had insane potential in my eyes. Hopefully Zed can achieve a similar feat (more likely targetting VS Code plugins?) or some other rich plugin ecosystem.
It was onivim2. Iirc it was a one-man show, and stopped when funding dried up. I also hoped to see a a lot from it. Maybe the dev took too much work on his plate, with an unproven language with limited libraries? https://github.com/onivim/oni2