I'd love to see the git blame logs for that one. Whoever wrote that code even before it had the bug was an incompetent cowboy hotshot who wanted to show off ho

I'd love to see the git blame logs for that one. Whoever wrote that code even before it had the bug was an incompetent cowboy hotshot who wanted to show off how pedantically he knew and could surf the nuances of syntax and optimize the code to have the smallest source file size by penny pinching brackets. "ALWAYS USE BRACKETS" is one of the oldest and wisest rules in the book, and this shows why. Anyone who actually writes security related code like that, blatantly ignoring important coding practices in the name of "aesthetic beauty" or however they rationalize omitting brackets, should be fired. I bet they're the same cowboys who fanatically prosthelytize JavaScript automatic semicolon insertion too, because that's another outlet for their obsession with showing off how clever they are to write code that requires them to deeply understand and consider every nuance of the syntax at every keystroke, instead of facing the fact that they or somebody who comes later might actually make a mistake, and coding defensively. Maybe they really are fucking geniuses who never make mistakes, but that's not true about everyone else who has to read and modify the code. Apple should go through all their code and fix it, and dock the salary of anyone caught not using brackets.