> Create a browser monoculture just to satisfy webdevs who are too lazy or shitty at their job to support two(2)!
I don't see why you have to be so nasty. I'm not lazy, nor bad at my job. Firefox has unique failures in standard compliance and the function of APIs. It's not just a matter of "supporting two browsers", it's a matter of working around the unique deficiencies of Firefox, for which there rarely exist equivalents in Chromium. For example, for the longest time, getBoundingClientRect and getBBox do not work properly for elements inside an SVG.
Still today Firefox misuses 1/60 unit fixpoint numbers for SVG geometry, which means that if you scale a <use> element larger than the geometry in the <defs>, it will be positioned incorrectly and/or misshapen; they could keep their fixpoints and still implement SVG correctly, but they instead just leave the bugs. There is little evidence that this follows any performance necessity, as Chromium and IE manage to render SVGs on the CPU considerably faster than Firefox does, while using floats in this role; Firefox barely runs properly on no-FPU computers anyway.
So shame on you for casting aspersions on web developers for not supporting this unpopular, IE-quality Netscape fork as easily as they support Chromium.
> Are you too young to remember the IE monoculture? Otherwise I cannot fathom how you could be so petty and short sighted as to suggest that Firefox become a chromium browser.
Are you maybe attributing the ill effects of the IE era to monoculture when they could be better explained by a single controlling interest? I don't think the current situation, where a set of related KHTML forks owned by competing companies make up about 90% of browser market share, is comparable to the IE6 situation.
> None of the bullshit you're talking about is more important than avoiding a browser monoculture. Not even close.
Can you please stop being so uncivil? It's totally unnecessary, and discourages people from engaging in good faith (since they can predict that you'll throw it in their face).
In any event. Chromium is not the new IE6, because it has infinite diverse controlling interests. If you don't like the direction Chromium is taking, and they won't take your patches, you can fork it or maintain a patchset. It is relatively cheap to fork Chromium, and definitely cheaper than developing your own separate browser engine for years, only to become almost competitive. If your patches are really that good, there's a great chance that they will make it upstream.
