It doesn't contain a lot of code not found in Chromium. Can you list some things that aren't open sourced as part of Chromium for Android or *nix operating systems? It's nearly just a branding swap. It doesn't have an impact on fuzzing the web sandbox, and they do that anyway.
Conversation
Of course I can't list things which aren't public, but there's at the very least three sources of additional code that I know about: The flash player, Widevine CDM, and NaCL. Additionally, there's also big differnces in multimedia codec support, as well as sandboxing differences.
2
That's not true. NaCL is open source and included in Chromium. The flash player and Widevine are separate plugins and work in Chromium. There are not sandboxing differences. What differences in codec support are you actually talking about? Chromium certainly supports H.264, etc.
2
Do you understand that Chrome developers are Chromium developers, and the Chromium development blog is the Chrome development blog? Chrome developers have .org emails. Chromium refers to the project, and Chrome to the branded product built from the sources.
1
I'm not talking down to you. I'm trying to understand why you're making these false claims about Chromium. I don't see how this is related to the conversation anyway, just like the FreeBSD kernel vs. Linux kernel conversation. You don't seem to disagree and just want to argue.
1
I used those as examples of cases where projects have drastically different resources put into bug discovery and triage. That's all.
Here are the NaCl sources by the way:
chromium.googlesource.com/chromium/src.g
Crash reporting, updates and other things like that are in Chromium too.
1
It supports both the Widevine and Pepper Flash plugins. I've used both. Distributions usually don't include crash reporting because they don't want to deal with that, and their package manager handles updates. Some distros don't enable various codecs, others enable them all.
1
There are definitely no sandbox differences. They aren't substantially different. Chrome is essentially a branded build of Chromium with things like the update system set up to point at Google's servers and various plugins bundled. It's built from the same source tree too.
1
They drop in the extra build configuration / code for setting those things up. I really don't see how any of this is relevant to comparing Chromium / Chrome vs. Firefox in terms of resources dedicated to finding bugs and amount of discovered bugs. It was an example of that.
I'm sorry if you find my examples offensive, but I don't really want to debate the relative merits of the software in those examples beyond what's relevant to the conversation. You can read my tweet as Chrome vs. Firefox or Chromium vs. Firefox. It doesn't matter either way.