It creates a compound literal [1] of type array of int, and initializes the specified array positions using designated initializers [2] with the results of calls to puts().
Using designated initializers without the = symbol is an obsolete extension.
When rewriting apps, people have a tendency to say: "well, Oldversion provides X. We could make a Newversion that provides X better, but that's hard so maybe X is actually bad? We should provide Y instead." Then they're confused when nobody with X needs wants to use Newversion.
It's OK to use X until Wayland has support for the missing features. I don't really care what I'm running. But it's clear that X is not in shape to see significant development (e.g. to support new needs) in the coming decades.
The number of registers available to the program is fixed in the instruction set. The program cannot address more registers without recompiling it to an extended instruction set.
Key word here being "might". What actually gets displayed is highly dependent on the performance of the program itself and will manifest as wild stuttering depending on small variations in the scene.
I've seen no game consoles that allow you to turn vsync off, because it would be awful. No idea why this placebo persists in PC gaming.
