> Imagine, for example, you’re creating a basic game. You might have one thread dedicated to updating the graphics on the screen
Has the author has never actually written a game? The majority of games are single threaded. You calculate the positions, moves, strategy of the AI, etc. etc. and then eventually render the frame. For years, certain releases of Doom and Quake were the benchmarks for games because they were some of the first to use multiple threads and could scale to multiple CPUs/processors.
Sure, modern games tent to be able to use more cores and have some independent threads, but the majority of the work typically still happens in the main event loop.
Has the author has never actually written a game? The majority of games are single threaded. You calculate the positions, moves, strategy of the AI, etc. etc. and then eventually render the frame. For years, certain releases of Doom and Quake were the benchmarks for games because they were some of the first to use multiple threads and could scale to multiple CPUs/processors.
Sure, modern games tent to be able to use more cores and have some independent threads, but the majority of the work typically still happens in the main event loop.