There are differences though. Anyone can take the Chromium web engine and build their own browser on top, with tremendous amounts of control. Heck, this is suc

There are differences though. Anyone can take the Chromium web engine and build their own browser on top, with tremendous amounts of control. Heck, this is such an attractive proposition that even Microsoft has done this. While the mono culture of a Chromium driven web is a huge problem, it's not the same as the IE problem. The biggest mistake IMO was the Firefox open source project focusing on building a browser as opposed to a web engine. Even nodejs was created on Chromium (and the difficulty of building node on Gecko was the primary reason why MS chose Chromium over Gecko). I suspect if we want to avoid a Chromium monoculture, we will need a similar split like the Netscape > Firefox one, where someone pulls out the Gecko rendering engine and builds an open source product/business on top of it.