[EPILEPSY WARNING] How fast should an unoptimized terminal run?
source link: https://www.youtube.com/watch?v=hxM8QmyZXtg
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
[EPILEPSY WARNING] How fast should an unoptimized terminal run?
[EPILEPSY WARNING] At the end of this video, I demonstrate colored text on colored background tiles. The reference renderer displays this benchmark so quickly that the screen appears to flash colors violently. If you are photo-sensitive, you may want to stop watching the video before I run the colored text demo. [/EPILEPSY WARNING]
Many modern terminals (like Windows Terminal, etc.) run extremely slowly - often hundreds or thousands of times slower than PC hardware allows. Yet for some reason, pointing this out leads to lots of strange excuses from developers, all of which are not true.
In this video, I demonstrate how a very simple (~3000 line) codebase written in a few days - and literally never optimized at all - still runs by default at thousands of frames per second under real-world conditions, while supporting features that many modern terminals don't, like right-to-left strings of Arabic combining Unicode.
The course mentioned in the video is Star Code Galaxy (https://starcodegalaxy.com).
The code for this reference rasterizer is available under GPLv2 on GitHub (https://github.com/cmuratori/refterm)
Show lessShow more
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK