Live data from Hacker News

Linux When?

zed.dev

101–110 of 169 posts

Re: Linux When?

#101

Earlier quoted context omitted.

Well it may have effect on ergonomics. Some people claim they cannot use 60Hz monitor after trying 144hz.

Well, that is usually refering to some form of "simulated fluid motion", not new characters appearing and disappearing. The only case where that kinda fluid motion would matter is when you have text scrolling by at semi-fast speeds.

I count myself among the people that would consider >60hz necessary.

For me, it's animations, especially if I'm dragging a window or just the mouse. On 60hz it's nauseating if I'm paying too much attention to the window I'm moving. It's goes completely away around 90-100 Hz (at least for me)

Re: Linux When?

#102

One question I don't think this post answers - why not use `winit`?

Simply put: historical artifact and we want to own the stack. Zed was first created when these abstractions where a lot younger, and a text editor needs certain features, like IME support, that weren't as common back then. Further, owning the stack we're built on gives us the flexibility to change the framework whenever and however we want, which we value more than the additional work it takes to re-implement things…

Makes sense, thank you for the thorough answer!

Re: Linux When?

#103
post #45

Earlier quoted context omitted.

Out of curiosity, how many of them run at 120 FPS? (honest question - I've never looked into it myself)

Honest question. What could you possibly do with a text editor at 120 fps that you can't do at 15 or 30? I can't think or type that fast and I can't read scroll back that fast either so I can't wrap my head around needing something like that.

Smoother scrolling?

Re: Linux When?

#104
post #85

Earlier quoted context omitted.

Cross platform toolkits, more than other software components incur massive tradeoffs. They’ve written one themselves, tailored to their needs and open sourced it along the way. I guess I don’t see the problem here. If one that’s existed for decades fits your needs better then use that.

Wgpu seems very very well loved & supported, is one of the most successful comings together of the graphics world in ages. I'd love to hear some actual critique of it, hear what people think are shortcomings, because it feels to an outsider like this is the fantasy land, that we're living in the better place now. https://github.com/gfx-rs/wgpu

Well, it's Rust. I am using TypeScript. I guess I am sticking with Electron. Maybe WebGPU can help me out.

Re: Linux When?

#105
post #40

am I supposed to know what zed is?

Why bother commenting instead of clicking the link and in the main navigation bar pressing the very clearly visible "ABOUT" button?

It's just common online courtesy to add to the title a short description of the project like (Zed, code editor) to save users some valuable time.

Re: Linux When?

#106

Earlier quoted context omitted.

Metal predates Vulkan. But also I'm pretty sure Apple doesn't care if an app is portable.

But AMD's Mantle predates both & was proposed & what lead to Vulkan. Apple saw the fork in the road & quickly scrambled to build their own thing. I'm kind of tired of this contention cropping up again and again. Technically true but insufficient & obfuscating more than revealing.

Sorry no. Vulkan literally did not exist. That's not obfuscation. It didn't even exist.

Had Apple adopted Mantle then where would they be now? Apple did what they do, took ownership of their own stack.

Re: Linux When?

#107

Earlier quoted context omitted.

Why bother commenting instead of clicking the link and in the main navigation bar pressing the very clearly visible "ABOUT" button?

It's just common online courtesy to add to the title a short description of the project like (Zed, code editor) to save users some valuable time.

And it's in the HN guidelines not to: https://news.ycombinator.com/newsguidelines.html

> please use the original title, unless it is misleading or linkbait; don't editorialize.

> If the title includes the name of the site, please take it out, because the site name will be displayed after the link.

> Please don't do things to make titles stand out, like using uppercase or exclamation points, or saying how great an article is. It's implicit in submitting something that you think it's important.

Re: Linux When?

#109
post #45

Earlier quoted context omitted.

Out of curiosity, how many of them run at 120 FPS? (honest question - I've never looked into it myself)

The question doesn’t make sense. They don’t rerender the buffer every frame. I assume zed isn’t doing that either as it would be horribly inefficient. I presume what is meant is that it can handle a redraw fast enough to be in the next frame. In which case the answer is: all of them. Drawing text is not the bottleneck for a GUI program, unless you have a god awful browser stack as your rendering engine.

> I assume zed isn’t doing that either as it would be horribly inefficient.

What are you supposed to do instead? Zed uses the GPU. It's not making calls to retained-mode widgets to individually reposition them, nor is it blitting into a buffer using the CPU. It's using the GPU which eats pixels for breakfast. You've been able to rerender the entire screen each frame for over a decade - just look at Windows 7 Aero, which ran on the laptops of 2009 for the exact same reason: it used the GPU!

Re: Linux When?

#110
post #101

Earlier quoted context omitted.

Well, that is usually refering to some form of "simulated fluid motion", not new characters appearing and disappearing. The only case where that kinda fluid motion would matter is when you have text scrolling by at semi-fast speeds.

I count myself among the people that would consider >60hz necessary. For me, it's animations, especially if I'm dragging a window or just the mouse. On 60hz it's nauseating if I'm paying too much attention to the window I'm moving. It's goes completely away around 90-100 Hz (at least for me)

I've had the privilege of using a merely 90Hz display and the difference is still incredible. It gives me input feedback much faster so my brain does not have to do as much buffering/prediction, everything feels a lot more direct. One would think a measly 5 milliseconds wouldn't amount to much, but for input feedback it absolutely does.

I do not suffer from nausea or motion sickness of any kind arising from computers or visuals in general, but I can still easily tell the difference between a 60Hz and 90Hz display. A few months ago I had the privilege of checking out the 120Hz displays on the new MacBooks and they're amazing.

Post reply on HN