Should we limit the FPS?

[lunacookies]

Terminal emulators such as Alacritty take as much data as possible from the program and only update the window at a certain refresh rate. If we limit pipes-rs to output at the same rate as the window, then we’ll save a lot of unnecessary stepping of the world when the window isn’t even updating. I guess the pipes are still moving during this time between window updates, which means this change would slow down pipe movement, but thereby make pipe movement speed consistent regardless of the terminal’s speed.

spin_sleep is perfect for both implementing this and an FPS meter.

[lunacookies]

I tried implementing this, but it doesn’t work because the terminal doesn’t display things instantly after flushing STDOUT, so the reported FPS is misleading and only accounts for pipes-rs’s processing and sending the data to be printed to the terminal. As far as I know, there isn’t a way to ensure that data has reached the terminal and has been displayed.