正在加载视频...
视频加载失败
First I optimized CPU, then memory, now I'm onto the renderers (Metal first). Scrolling Neovim now sustains ~175fps easily (vsync off of course). More room for improvement, but this is already best-in-class (I can't find a terminal at the moment that does better on macOS). The road to get... show more
10 条评论

More FPS means less CPU spent on single frames, right? Scaling that to 100k-s of users means less energy used in general. Every watt counts. Doing your part for the <2°C goal. Or am i too optimistic here why optimizations matter? 😉

Haha, well, the first part is right. :) CPU usage for both idle and saturated screen changes is significantly lower. Whether that'll make any sort of meaningful difference... well... lol.

I need Ghostty in my life. Patiently awaiting my day in Discord

Let's goooo!

Very nice! Must look really nice on a high frequency display when scrolling backbuffer with pixel increments

High FPS in terminal does matter. Anyone who asks why doesn't get it.jpg.

dope results! out of curiosity, is that monitor helper in the right side something you developed yourself to debug?

Nope, just run any program that uses Metal with `MTL_HUD_ENABLED=1`. Its built-in to macOS.

FPS does totally matter. I quit neovim for vscode because how slow redrawing was in the terminal and how every plugin was competing with each other.

If you ever go back to neovim, `set notermsync` is a huge thing too. This prevents internal escape sequence buffering. May result in tearing depending on the terminal but for fast terminals (like Ghostty!) it dramatically improves fps and latency.
