Live data from Hacker News

Zed on Linux Is Here

zed.dev

191–200 of 703 posts

Re: Zed on Linux Is Here

#191

Just a suggestion. One of the best features of pure text editors (and incredible, not all of them implement it) is autosave keeping the "unsaved" state of the file. For example, if you make some changes in a file (new or not), don't save the changes, close and open the editor, the state of the opened files are kept like I never had closed the editor. The unsaved files are still unsaved. New edited files are still the…

Atom worked that way as well

Re: Zed on Linux Is Here

#192

Earlier quoted context omitted.

| It is running in xwayland though It definitely isn't on my system, and I did not touch the configs at all; are you sure about that?

Fairly positive due to blurry cursors, but I have no way to verify.

If you run xeyes and the eyes follow your cursor when it's above the application you want to test, it's running under xwayland. If they don't follow your cursor, the application is running under native Wayland.

Re: Zed on Linux Is Here

#193

I tried zed for a few weeks because I'm generally sympathetic to the "use a native app" idea vs Electron. I generally liked it and its UX but: 1. VSCode is pretty damn fast to be honest. Very rarely is my slowdown in my work VSCode loading. Maybe I don't open very large files? Probably 5k lines of typescript at most. 2. Integration with the Typescript language server was just not as good as VSCode. I can't pin down e…

A few weeks ago I had this giant json text blob to debug. I tried Gedit first, and it just fell over completely. Tried vim next, and it was for some reason extremely slow too, which surprised me. VSCode loaded it nearly immediately and didn't hang when moving around the file. I have my complaints about VSCode, but speed definitely isn't one of them.

Did you have some plugins in vim? It is very odd if it was slower in this scenario.

Re: Zed on Linux Is Here

#194

Earlier quoted context omitted.

I haven't tried Zed and am unlikely to, but I get 238 characters of fantasque sans mono 11pt on my 1200p screen, so I could give up those spaces and still have two vertical panes (assuming Zed supports vertical panes and the file-browser isn't duplicated).

I think lots of people are comfortable with smaller fonts, but I find myself genuinely straining my eyes too much and getting headaches if I go smaller than this, and I already wear glasses (although I should probably update my prescription).

Oh, there's no "right answer" to font size, but the fact that my size would work on a 1200p screen (and many of my coworkers have significantly larger screens and younger eyes than I) could go towards explaining why the sidebar is on by default and the gutter is so huge.

Re: Zed on Linux Is Here

#196

Just a suggestion. One of the best features of pure text editors (and incredible, not all of them implement it) is autosave keeping the "unsaved" state of the file. For example, if you make some changes in a file (new or not), don't save the changes, close and open the editor, the state of the opened files are kept like I never had closed the editor. The unsaved files are still unsaved. New edited files are still the…

I wouldn’t mind auto saving and allowing me to undo changes from the previous session.

Re: Zed on Linux Is Here

#197

Earlier quoted context omitted.

It's free software in letter, but not in spirit. True free software doesn't lock out non-official builds for zero technical reasons.

what about vscodium? for that reason, what was iceweasel?

There is some sort of vendor lock-in VSCode. It at least used to be extremely difficult to make GitHub Copilot to work with codium. There is something closed source in VSCode that makes the difference.

It was so difficult to maintain, that I ended up switching to VSCode. So the ”lock-in” worked.

Re: Zed on Linux Is Here

#198
post #193

Earlier quoted context omitted.

A few weeks ago I had this giant json text blob to debug. I tried Gedit first, and it just fell over completely. Tried vim next, and it was for some reason extremely slow too, which surprised me. VSCode loaded it nearly immediately and didn't hang when moving around the file. I have my complaints about VSCode, but speed definitely isn't one of them.

Did you have some plugins in vim? It is very odd if it was slower in this scenario.

Not to my knowledge, outside of whatever Debian comes with. Keep in mind this was on a Chromebook - so it would have been running in a VM on a rather memory restricted system. That said, VSCode would have been running in the same parameters.

Just found the file. 42MB on a single line. Takes 5 seconds to open in vim, and about 3 seconds for the right arrow to move the cursor one char over. Nothing like gedit, but slower than I expected.

Re: Zed on Linux Is Here

#199

I tried zed for a few weeks because I'm generally sympathetic to the "use a native app" idea vs Electron. I generally liked it and its UX but: 1. VSCode is pretty damn fast to be honest. Very rarely is my slowdown in my work VSCode loading. Maybe I don't open very large files? Probably 5k lines of typescript at most. 2. Integration with the Typescript language server was just not as good as VSCode. I can't pin down e…

A few weeks ago I had this giant json text blob to debug. I tried Gedit first, and it just fell over completely. Tried vim next, and it was for some reason extremely slow too, which surprised me. VSCode loaded it nearly immediately and didn't hang when moving around the file. I have my complaints about VSCode, but speed definitely isn't one of them.

For this kind of stuff Sublime has always been extremely good.

But I still struggle to find a reason to not use neovim, it's replaced all my editors.

Post reply on HN