To play devil's advocate, the very example in the article is a misuse. Not only is a difference of less than 1% in code speed insignificant (local timings), but a do...while loop displays the intent (looping) better.

In C at least. Anyway, that's probably due to the significant amount of discussion about goto. Perhaps "ironically" goto is a good feature only because it's criticized enough so that it's typically used correctly?

> Perhaps "ironically" goto is a good feature only because it's criticized enough so that it's typically used correctly?

there are no good/bad features, there are only good/bad programmers.