| > Should we insist that browsers also be built with different languages In a perfect world, yes. Then you might not get standards written entirely around ease of implementation in C++, leading to crazy behavior just because it happened to be the simple thing to do in that language. > if not just that Chromium/Chrome are somehow bad for the web? What's bad for the web is monoculture, because then people start building sites that rely on quirks of that monoculture that are not codified in a standard. And then if something better comes along it's a long uphill battle to get that something better adopted, because it has to duplicate those quirks. For example, there is no way something like Servo would be able to happen if we had a Blink monoculture on the web, and I seriously doubt that Blink will be able to parallelize to the extent that Servo is planning to and that I think the web needs in the future. For another example, once you have an engine monoculture, the developers of that engine become gatekeepers for what's possible on the web. We saw that once already with IE. While Google is not likely to shut down development of Chrome in the near future, they have their own priorities (e.g. getting video DRM implemented is a lot more important to them than anti-tracking countermeasures), so unless you think those priorities are perfect for the web you should be against them having a stranglehold over what ends up in the web platform. Just like you should be against any other entity having such a stranglehold. It was bad when Microsoft was there, it would be bad if Google were there, and it would also be bad if Mozilla were there. |