News for hackers. Stuff that matters.
Re:Google isn’t the company that we should have handed the W... by jcranmer on Tuesday December 18, 2018 @05:42PM (#18711292)
Google effectively has the right to veto patches into Chromium. In the worst case, Google could fork Chromium, and since Google controls the build artifacts, in a dispute between Google and Microsoft, it's Google who wields the power.
Re:Google isn’t the company that we should have handed the W... by vbezhenar on Tuesday December 18, 2018 @06:58PM (#18711777)
How is it Google? Anyone could just fork Chromium and do anything about it, it's open source after all. Microsoft could buy people from Google if they wanted to, they probably could buy an entire Chrome team. Google has some control over Chromium engine right now, but this control is fragile. It's the same control that Oracle has over MySQL. Abuse it and you'll have MariaDB instantly. Abuse Java control and you'll have plenty of companies forked Java and ready to provide real LTS for Java 8. It'll be the same for Chromium.

The best outcome would be to have some Non-commercial organization funded by Google, Microsoft, Yandex and other big players who benefit from Chromium which would have some kind of independence. But current situation is not that bad.

There are other things than just source code license. May be Google has patents for Chromium sources and could use them to forbid fork? Then it's a bad situation but I didn't heard about that point of view yet.

Re:Google isn’t the company that we should have handed the W... by jacques_chester on Tuesday December 18, 2018 @07:25PM (#18711914)
Your examples of successful forks are due to branding amongst technologists, who understand the concept of a fork and who were following the most-trusted of the descendents (another example being Hudson and Jenkins).

Consumer brands are not as easy to fork. If Coca-Cola opensourced their recipe and then faced a fork by Examplesucre, I don't think anyone will really be betting against Coke.

Similarly, the longevity of mainline integrity for Linux relies heavily on the fact that it is a trademark and that the trademark holder (Linus) is trusted with it. Fork Linux as much as you please, basically nobody will care.

Google's power over Chromium comes from its power over Chrome. If you don't think that's true, fork it yourself and prove us all wrong.

Re:Google isn’t the company that we should have handed the W... by microtherion on Wednesday December 19, 2018 @12:04AM (#18713162)
> Fork Linux as much as you please, basically nobody will care.

Last I heard, Android was doing OK…

Similarly, I should think that Microsoft still has considerable clout in what browser Windows users will use by default (although I'm not sure what exact legal restrictions they currently have to observe re: bundling of browsers).

Re:Google isn’t the company that we should have handed the W... by jacques_chester on Wednesday December 19, 2018 @12:16AM (#18713222)
Android is a better example of forking Java, to be honest.
Re:Google isn’t the company that we should have handed the W... by Wowfunhappy on Tuesday December 18, 2018 @07:00PM (#18711791)
> How is it Google?

Because a majority of users are using Google Chrome.

You're right, if Microsoft could convince chrome users to switch to Edge, they would have more power. Things can change, but I don't see how this would happen.

Re:Google isn’t the company that we should have handed the W... by Micoloth on Tuesday December 18, 2018 @05:56PM (#18711386)
But, isn't it reasonable to assume that microsoft will get hold of the Whole codebase if they embrace this as their new default browser? I mean its Microsoft we're talking about..
Re:Google isn’t the company that we should have handed the W... by tracker1 on Tuesday December 18, 2018 @08:17PM (#18712205)
Well, it's likely they'll only use the core rendering engine (Blink, formerly Webkit) and wrap their own application around it. Hell, with all the applications they've released or are working on with electron (Teams, VS Code, SQL Operations Studio), I'm far less surprised.

I've been hoping they'd come up with for a more shared model for applications in the node/npm ecosystem similar to Adobe's Air. If MS did a good job of such a platform from open-source with tooling to build applications that run everywhere, more power to them.