| ▲ | keyle 7 hours ago | |
This is cool and reminds me of the old ascii art editors; although this appears more geared towards technical documentation than art. Not sure why the title has to mention 144fps, which is of course dependant on the computer specs, the terminal emulator, and the screen rendering the program... If you've got a problem rendering ascii fast, I got news for you... | ||
| ▲ | xlii an hour ago | parent | next [-] | |
Well it isn't that simple :) It mentions 144FPS, because of scrolling/zooming events. If there's a key-by-key panning then probably you need 1 frame and you're good. Macbook's Pro touchpads generate events with 150hz - and in order to maintain "butter smooth" FPS has to follow. Number of cells on screen matters: rendering 80x80 is not a problem. After zooming out and 1000x1000 on screen panning with 150FPS is straightfoward. In the end there is a deterioration of user experience when jank in scrolling, zooming and even typing happens. Thus ceiling right now is around 144FPS, mostly because ~6ms budget (on M2 Macbook and 4K 144hz display). 60hz refresh rate 60FPS is an easy mode ;-) | ||
| ▲ | vidarh 2 hours ago | parent | prev [-] | |
You certainly will have a problem rendering ascii fast in lots of terminals if you keep re-rendering things that haven't changed, though, so I hope that's not what they mean by giving FPS numbers | ||