could you expand on why you think mozilla's engineering practices suck ?
I have sometimes had a similar feeling, but I have too little competence to be a judge of that.
Because they are not as rigorous as Google's. At Google every commit is read and reviewed before it lands in source control. And they have an entire team dedicated to building the testing infrastructure, so they can do things like testing Flash against every possible input to see if there are any security holes. (There were.) Google is all about being super careful about every line of code. I don't know for a fact that Mozilla isn't, but the quality of the code that I've read in each browser makes me think Google has a better process. But I could be wrong.
Jesse and company have been writing lots of other fuzzers that aren't public yet as well...
Seriously, what you described above (pre-checkin code review and fuzz-testing) are all standard industry practices for web browsers and have been for years.
