4 ms·

Or, it was a stupid mistake. The kind that happens every day, in every program, in the known universe. If we're going to entertain conspiracy theories, I favou

Or, it was a stupid mistake. The kind that happens every day, in every program, in the known universe. If we're going to entertain conspiracy theories, I favour "A rogue Google agent snuck in to Apple headquarters and edited the file whilst the user was out for lunch". Or perhaps Zergloids. Come on people, we're getting as bad as Slashdot over here!

yuvadam 13y ago
Did you look at the diff? Did you see that it is the only diff in that hunk? Do you not agree that that is - at the very least - suspicious?
- archgrove 13y ago
  Yes, I looked at the diff. A diff like the author probably had been looking through all day. You've never missed a line? They probably thought it was just whitespace changes or, you know, just missed it entirely. If we're going to claim this is deliberate, then the same accusation can be levelled at every security bug ever introduce in an edit. This is not evidence, it's just trolling.
- mef 13y ago
  Why does the fact that it's the only change in that hunk make it suspicious?
- deleted 13y ago
  [deleted]
- lstamour 13y ago
  Not really, most editors support the ability to duplicate a line using CMD+D, including AppCode by JetBrains. In my case, using Colemak, S is mapped to D, and so if I'm in the wrong keyboard layout, I'll go to save and end up duplicating a line, then saving by hitting the right key. If I'm not careful, I'll have saved a duplicate line without noticing. Similarly, given how the rest of the changes seemed to be attempts to rename and clean up the API, I expect that it was a junior intern cleaning up code as a whole. It would be more interesting to see the history of the commits, but that's not public (that I know of). It does highlight how we get that data with Google's Android, even though the development and release process is basically the same.

4 ms·

Or, it was a stupid mistake. The kind that happens every day, in every program, in the known universe. If we're going to entertain conspiracy theories, I favou

by archgrove 13y ago

yuvadam 13y ago
Did you look at the diff? Did you see that it is the only diff in that hunk? Do you not agree that that is - at the very least - suspicious?
- archgrove 13y ago
  Yes, I looked at the diff. A diff like the author probably had been looking through all day. You've never missed a line? They probably thought it was just whitespace changes or, you know, just missed it entirely. If we're going to claim this is deliberate, then the same accusation can be levelled at every security bug ever introduce in an edit. This is not evidence, it's just trolling.
- mef 13y ago
  Why does the fact that it's the only change in that hunk make it suspicious?
- deleted 13y ago
  [deleted]
- lstamour 13y ago
  Not really, most editors support the ability to duplicate a line using CMD+D, including AppCode by JetBrains. In my case, using Colemak, S is mapped to D, and so if I'm in the wrong keyboard layout, I'll go to save and end up duplicating a line, then saving by hitting the right key. If I'm not careful, I'll have saved a duplicate line without noticing. Similarly, given how the rest of the changes seemed to be attempts to rename and clean up the API, I expect that it was a junior intern cleaning up code as a whole. It would be more interesting to see the history of the commits, but that's not public (that I know of). It does highlight how we get that data with Google's Android, even though the development and release process is basically the same.