Hacker News Reader

Hey nottorp. Antonio here, author of the post.

Zed and GPUI use energy very judiciously and only perform updates when needed. The idea is that we can render the whole application within ~8ms, and that shows everywhere: from typing a letter to scrolling up and down in a buffer. However, if the editor is sitting there idle, we won't waste precious CPU cycles.

Thanks for the feedback!

Will you allow developers access to your GUI framework? What about open-sourcing it?

Yeah, might want to edit the title a bit. Or not, considering these concepts are getting lost.

I mean, the win16 api from ages ago had support for invalidating specific screen regions etc. It probably got lost somewhere in the transition to javascript...

It's not about rendering static screens at 120Hz, but rendering anything that's animated at a smooth 120Hz.

"Because it looks good" is probably the most popular reason.

But if nothing changes it looks as good at zero fps :)

Edit: Yay, it's a text editor. What happened to only redrawing the line that's being edited and the status indicators?