Microsoft Edge and open source collaboration
131–140 of 304 posts
Re: Microsoft Edge and open source collaboration
#132"Embrace, extend, and extinguish"? At this point, with google, I'm not even sure if it's a bad thing, if true.
Re: Microsoft Edge and open source collaboration
#133Re: Microsoft Edge and open source collaboration
#134On one hand, this creates a platform that is more or less the standard of the web. On the other hand, this only gives Google more control of the web. I really wish that instead of doing this Microsoft would just stick with EdgeHTML and maybe open-source it.
Google should not be happy about this.
Makes it harder for them and everyone else to push web standards forward.
Re: Microsoft Edge and open source collaboration
#135Earlier quoted context omitted.
Because then any pull request introducing something into Chromium essentially becomes the web standard. For example, Google has a ton of influence on the project. If they want to, they can introduce something that benefits their services but eschews the web standard.
but if Microsoft is moving to Blink, wouldn't they, as well, have (as you say) influence on the project? What, really, is a downside to having an open-source web engine that all browsers use? I'm failing to see one. The web would become less fragmented; the web standard would be (only slightly) irrelevant, and we would move forward without having to deal with browsers interpreting the spec/standard differently, which…
No.
1. Chrome will remain the dominant web browser
2. the Chromium repository itself is owned by Google
The only leverage Microsoft is in forking Chromium, but that does nothing to Chrome's market.
Google themselves forked WebKit when they couldn't get along with Apple. And that was back when Chrome wasn't as pervasive.
So what makes you think Google would give a crap about Microsoft today?
Re: Microsoft Edge and open source collaboration
#136Earlier quoted context omitted.
This is step 2: Extend.
It's step 1: embracing the open standard. They'll extend it next. Another commenter already pointed out that could be as easy as just using Bing to send revenue to them using Google's tech. They'll come up with other ideas. Far as open-sourcing their stuff, I think they're holding off on that to preserve their profitable lock-in in legacy market. Harder to clone their key dependencies if the code isn't open. Even ope…
Ah the only second ISO Standard for the same thing. With transparent definitions like: if option XYZ is set, render the output like Word 97.
Blatant corruption by a standard gremium.
Re: Microsoft Edge and open source collaboration
#137Re: Microsoft Edge and open source collaboration
#138I'm assuming I'm not the only one who's afraid of Blink becoming the new Internet Explorer; instead of people following a web standard, they'll follow what's Chrome-compatible. It's still better because Chromium is open-source, but I do worry that we're going to have a problem in the future with a lot of broken sites (YTMND-style).
Blink is open source- you want to encourage innovation in the usability and utility of the browser and let people compete on market share of their browser product not how people’s web apps that run on that platform work or don’t work - The key is it’s open we’ll never have another IE6. Anyone can compile Blink. Look Microsoft is focusing on getting it to work on arm- cool. This is the opposite of locked to windoze only.
Re: Microsoft Edge and open source collaboration
#139Re: Microsoft Edge and open source collaboration
#140Earlier quoted context omitted.
> " 1. If Google opts to steer Chromium in a way that the community finds objectionable, could the community stop it? " The answer to that is obvious. Of course not. Google owns Chromium's repository. Even if the "community" decides to fork Chromium, Google owns Chrome, so any fork of Chromium is completely irrelevant. That's because people download and install Chrome and not obscure Chromium forks. And that is why w…
“Obscure Chromium forks” – like Samsung Internet and Edge? Remember: Chromium itself is an “obscure fork” of WebKit...
Yes, exactly like those two.
>> "Remember: Chromium itself is an “obscure fork” of WebKit..."
Actually when Google forked WebKit, Chrome wasn't obscure at all. But yes, that's the perfect proof that Google doesn't want to cooperate when they aren't pulling the strings.