> 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.
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.