(no title)
breadwinner | 4 months ago
If you want to talk about perf in the context of a text editor show me how big of a file you can load--especially if the file has no line breaks. Emacs has trouble here. If you load a minified js file it slows to a crawl especially if syntax highlighting is on. Also show me how fast the start up time is. This is another area where Emacs does not do well.
So Zed is available on Windows--but only if you have a x64 processor. Lots of people run Windows on Arm64 and I don't see any mention of Arm64. This is where the puck is heading.
Also noticed Emacs key binding is in beta still.
poly2it|4 months ago
Also, I do not believe Windows on Arm64 is a very large demographic? Especially for developers, unless they're specifically into that platform.
TiredOfLife|4 months ago
The latest benchmark I could find is 2022 and it's nowhere as bad as you claim
https://github.com/microsoft/vscode/issues/161622#issuecomme...
marcosdumay|4 months ago
Once you are beyond a bare minimum, every other speed metric is more important. Zed does really well on many of those, but some depend on the LSP, so they become the bottleneck quickly.
breadwinner|4 months ago
adastra22|4 months ago
STKFLT|4 months ago
adastra22|4 months ago
I have never, ever felt “latency” in editor UI. Any editor UI. It’s editing text for Pete’s sake. I can only type so fast, or read so fast.
breadwinner|4 months ago
1718627440|4 months ago
bschwindHN|4 months ago
Me! Frame rate and input latency are very important for a tool I use for hours every day. Obviously that's not the only feature I look for in an editor but if an editor _doesn't_ have it, I skip it. I also try to work on devices with 120Hz displays and above these days.
1718627440|4 months ago
jay_kyburz|4 months ago
scuff3d|4 months ago
But waaaaah they don't support a processor that accounts for probably less then 10% of Windows Machines
breadwinner|4 months ago