News for hackers. Stuff that matters.
Re:Switching to DuckDuckGo and Firefox by jmillikin on Friday July 12, 2013 @05:31PM (#6035335)
The actual comparison would be between the Chrome binary size and the Chromium binary size, which is quite small if you exclude embedded graphical resources.
Re:Switching to DuckDuckGo and Firefox by kryten on Friday July 12, 2013 @05:36PM (#6035355)
Actually that's a really bad comparison.

The binary size may be similar but that doesn't mean the content is. Consider the two cases below to back up my assertion:

   000000WE_COME_IN_PEACE000000000000000000
   000000WE_COME_IN_PEACE_SHOOT_TO_KILL0000
Re:Switching to DuckDuckGo and Firefox by jmillikin on Friday July 12, 2013 @05:44PM (#6035410)
I don't understand your point. If there were such a difference between Chromium and Chrome, then it would surely show up in a diff of the binaries' disassemblies. The size of the binaries doesn't matter, because (assuming you trust the Chromium source and your local system) only the difference between the two is relevant.
Re:Switching to DuckDuckGo and Firefox by kryten on Friday July 12, 2013 @05:52PM (#6035452)
My point is that it will show up in a diff of the binaries.
Re:Switching to DuckDuckGo and Firefox by jmillikin on Friday July 12, 2013 @06:54PM (#6035829)
Isn't that what I said?

I said that the binaries could be diffed, then you responded that finding a difference is unlikely because the binary is very large. I don't understand what the absolute size of the binaries has to do with being able to compare them.