5 ms·
This is great! One question: when would you need 60 FPS in a terminal? What CLIs or usages does this make a difference for?
by sbjs 8y ago
This is great! One question: when would you need 60 FPS in a terminal? What CLIs or usages does this make a difference for?
- anik3t__ 8y agoThis is useful while catting a large file/tcpdump on an interface with lots of packets, etc.
- artursapek 8y agoIf that benefits from 60fps, doesn't that imply that it's too fast for you to read in the first place?
- toast0 8y agoIt's possible to look for anomalies in scrolling text that's passing by much faster than can be read. (I'm not convinced that requires opengl, but one reason I use iterm is because doing this on terminal with default settings quickly freezes because of infinite scroll. I presume you can turn that off, but easy copy/paste and minimum contrast settings are nice too. Also, the progress meter on large pastes is suprisingly useful.
- anik3t__ 8y agoTrue. I have set triggers that color the text / give out osx notifications if there is a string somewhere like Error/Exception.
- dev_dull 8y agoIt’s easier on your eyes to follow and just looks aesthetically better also.
- mynameisvlad 8y agoIs it? Playing around with the Metal renderer and FPS monitor, I rarely go above 30fps in day-to-day work, and most of the time I'm hitting 10-15fps. There's only certain use cases where you'll actually reach 60fps.
- saagarjha 8y agoI get 60 FPS when scrolling.
- mynameisvlad 8y agoEven when scrolling, I rarely hit 60. Most of the time, I'm staying in the 40 range and hit 60 for one or two frames. The FPS meter only works with the Metal renderer, so I can't directly compare it and the CPU renderer, but just from a subjective perspective, I notice slightly worse performance from the CPU renderer while scrolling, but nothing major. Beyond that, though, how often are you scrolling, and how buttery smooth does that have to be to be a good experience? While it does seem smoother side-by-side, I'm not blown away by the difference.
- panic 8y agoIf the terminal is double-buffered, it'll reduce input lag noticeably (16 ms vs 33).
- snuxoll 8y agoYou mean triple buffered, double buffering introduces an extra frame of input lag (16ms @ 60FPS).
- genghizkhan 8y agoI find neovim to be quite laggy while scrolling without the metal renderer. It's the only reason I was so happy about this feature landing.
- rane 8y agoIt's not so much that you need 60 FPS, but in my use GPU rendering makes editing in vim much more responsive. It basically brings terminal vim on a par with MacVim in rendering speed.