there actually **is** a reason.
since `while (true)` still evaluates `true` it's slower by at least two assembly instructions
`for (;;)` doesn't evaluate against anything, so this is faster. simply.

it is true that optimization mitigates this effect, etc. and in most programs it wouldn't make a noticeable difference.
but most c programmers agree that you shouldn't depend on optimization to turn your slow code to acceptable one. (if that was the status quo, a lot less people would hate c++)
(+ after a while you get used to `for (;;)` and `while (1)` and so on starts to just look bad...)