Comment by bayindirh
8 months ago
Getting Microsoft to use a new engine and contribute back to the original repository is better for diversity, but forking and running away with it is certainly not.
8 months ago
Getting Microsoft to use a new engine and contribute back to the original repository is better for diversity, but forking and running away with it is certainly not.
> Forking and running away with it is certainly not
If your goal is browser diversity, this would take an ecosystem of 2 browser engines and turn it into an ecosystem of 4. That seems in-line with the goal of browser diversity.
Currently we have an ecosystem of two browser engines, yes. One of them is weaponized against users by its designers, both in its open and closed form.
Having 4 (or 3.5 more realistically) browser engines where 2 of them weaponized against its users doesn't change things.
Instead, we should have 3 (or 2.5) browser engines where only one of them is (and can be) weaponized against its users. This is what brings diversity and change.
> Getting Microsoft to use a new engine and contribute back to the original repository is better for diversity
Oh no no no. We don't need microsoft contributing anything into this. They will mess up everything and push their agenda.
Ideally, yes. Microsoft should stay away from this, but I wanted to highlight that adopting a technology doesn't automatically make it better for diversity.
Google was almost killing Go overnight because they wanted more user data from people using the language.