We Have to Start Over: From Atom to Zed • Hacker News Board

Re: We Have to Start Over: From Atom to Zed

#151

Post by hprotagonist » Sat, Feb 17, 2024, 7:07 PM UTC

losvedir wrote: post #146

I don't use Zed, but I noticed José Valim using it when he was live streaming a coding session. I mostly use VSCode, but one feature he used in Zed was really compelling: he did a "Find All", which was similar to VSCode in that it opened a results pane with snippets from all the files that matched, but then he was able to edit the snippets directly from there, and was able to use multi-cursor editing and all the othe…

emacs has had occur and multi-occur since the 80s that can do this. it’s amazing.

more recently, interfaces to tools like ripgrep also have the ability to have an editable mode, super handy for refactoring.

(and of course you can edit file names in bulk, too ..)

https://www.masteringemacs.org/article/searching-buffers-occ...

https://rgel.readthedocs.io/en/latest/

https://www.gnu.org/software/emacs/manual/html_node/emacs/Wd...

Re: We Have to Start Over: From Atom to Zed

#152

Post by pimlottc » Sat, Feb 17, 2024, 7:33 PM UTC

mplewis wrote: post #145

notso411 wrote: post #130

Earlier quoted context omitted.

Why bother with accessibility. If a disabled wants to use an IDE, use a different one??

Accessibility helps all users, not just disabled users.

Which is to say, we are all (temporarily, situationally, eventually) disabled in some way

Re: We Have to Start Over: From Atom to Zed

#153

Post by mixmastamyk » Sat, Feb 17, 2024, 7:34 PM UTC

8organicbits wrote: post #74

noodlesUK wrote: post #50

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?

sshfs solves most of these problems and I’ve found it good enough. Better than switching to a partly proprietary editor anyway.

Re: We Have to Start Over: From Atom to Zed

#154

Post by difflens » Sat, Feb 17, 2024, 7:40 PM UTC

losvedir wrote: post #146

I don't use Zed, but I noticed José Valim using it when he was live streaming a coding session. I mostly use VSCode, but one feature he used in Zed was really compelling: he did a "Find All", which was similar to VSCode in that it opened a results pane with snippets from all the files that matched, but then he was able to edit the snippets directly from there, and was able to use multi-cursor editing and all the othe…

Hmm maybe I don't understand fully, but can't you do this in VSCode by doing a `Find And Replace All`? (Cmd + Shift + F on Mac)

Re: We Have to Start Over: From Atom to Zed

#155

Post by mixmastamyk » Sat, Feb 17, 2024, 7:42 PM UTC

shp0ngle wrote: post #147

digdigdag wrote: post #40

Before 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…

This actually looks very reasonable...?

It’s not unreasonable.

The thing is every time you load company proprietary code and/or sensitive data you better make sure you don’t hit the share button as well.

Not the end of the world but also something we didn’t have to think about until recently. That pushing a button (other than delete) could potentially get you fired.

Re: We Have to Start Over: From Atom to Zed

#156

Post by Szpadel » Sat, Feb 17, 2024, 7:48 PM UTC

yoyohello13 wrote: post #143

Szpadel wrote: post #138

Earlier quoted context omitted.

I'm not surprised that most of rust guis are not a11y friendly, there is no established gui library yet, none of them I would call mature yet Not long ago there weren't any gui libraries that wouldn't be just binding to existing C framework or was in proof of concept state of lifecycle I'm sure this situation will improve in the future and I understand frustration of someone that rely on a11y features, but you need t…

System76 is making headway getting a11y accessibility for Cosmic Desktop. They are doing a lot of good work in the Rust gui space.

Agree, I think they might shape first mainstream rust gui library.

They are doing amazing job with whole desktop environment. I'm yet to check first hand their work, but so far looks very promising

Re: We Have to Start Over: From Atom to Zed

#157

Post by a_wild_dandan » Sat, Feb 17, 2024, 7:51 PM UTC

briandw wrote: post #121

I really love native apps, but I'm stuck using VS code for now. It just kills me to see how much power goes to blinking the cursor in VS code. I tried Zed for a bit but couldn't make it work. I loved that its so light weight and fast. Looking my all my VS code processes it 3GB vs Zeds 300MB. 1/10 the ram is a meaningful difference. However I really need the Jupyter Notebook support that VS code provides. I'm also too…

I guess that I'm lucky. I presently have multiple VS Code projects open (local & remote), and a Notebook running, and rarely break ~650MB -- less than 1% of my Macbook's memory. Maybe everyone has more extensions on than I do or something.

Re: We Have to Start Over: From Atom to Zed

#158

Post by peoplefromibiza » Sat, Feb 17, 2024, 7:52 PM UTC

ncruces wrote: post #85

peoplefromibiza wrote: post #47

Earlier quoted context omitted.

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

Startup would have to be terrible for me to bother. 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.

> Startup would have to be terrible for me to bother.

that's just the first noticeable difference.

but there have been instances lately where opening, editing and saving the file took me less time with zed than just open it in VS Code and waiting for it to be ready for inputs

> VS Code starts in under a couple of seconds

I am talking about relative speed differences. Imagine you open the same code base and the editor is ready in half a second. going back to the "slower" one would be unbearable.

now admittedly zed is no way near to the extensibility of VS Code so it is probably doing less and that's where probably much of the speed difference comes from, but it can't really be overlooked once you experienced it.

Re: We Have to Start Over: From Atom to Zed

#159

Post by tonis2 » Sat, Feb 17, 2024, 7:54 PM UTC

mplewis wrote: post #145

notso411 wrote: post #130

Earlier quoted context omitted.

Why bother with accessibility. If a disabled wants to use an IDE, use a different one??

Accessibility helps all users, not just disabled users.

Which accessibility features are you most commonly using ? Just wondering, what are the most used accessibility features, that new GUI-s don't have.

Re: We Have to Start Over: From Atom to Zed

#160

Post by fatboy » Sat, Feb 17, 2024, 7:57 PM UTC

losvedir wrote: post #146

I don't use Zed, but I noticed José Valim using it when he was live streaming a coding session. I mostly use VSCode, but one feature he used in Zed was really compelling: he did a "Find All", which was similar to VSCode in that it opened a results pane with snippets from all the files that matched, but then he was able to edit the snippets directly from there, and was able to use multi-cursor editing and all the othe…

In VSCode if you do super-shift-f for find-in-project, at the top of the results pane, just right of where it's marked "x results in y files" there's a link button titled "Open in editor" which I believe does what you're describing. I'd actually forgotten about it until I read your comment so I'll start using it again now.