Funny that minor side project of KDE is now responsible for the vast majority of today's Internet traffic. Did the original authors of KHTML ever receive a single dime for their work?
I wonder how much of KHTML is even left in WebKit/blink.
Microsoft Edge and open source collaboration
141–150 of 304 posts
Re: Microsoft Edge and open source collaboration
#142It's crazy! This is not the Microsoft from ~5 years ago. They have really changed! Opening up to linux, cross-platform apps, open sourcing tech, open sourcing their patents(!), and now using open source chromium for MS Edge? Dam. I never thought I'd see the day...
Re: Microsoft Edge and open source collaboration
#143Earlier 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...
Don't forget Opera is a re-skinned Chrome.
Re: Microsoft Edge and open source collaboration
#144Earlier quoted context omitted.
> Edge was only available to Windows users. And still, it was some competition to Chrome and Firefox. > encourage everyone to use Firefox. Which can be done while also lamenting the loss of a Firefox competitor, especially when said loss gains Firefox nothing.
MS could have chosen to base their platform on Firefox, but they chose to go with Chromium. We can lament the passing of Edge, but I wonder how people would have felt if instead of Edge they just had this announcement as the replacement for IE. Would we have cared? No one seems to miss IE.
> MS could have chosen to base their platform on Firefox, but they chose to go with Chromium.
MS went with Chromium because they want that implicit "best viewed in Chrome" compatibility.
Re: Microsoft Edge and open source collaboration
#145it seems like a lot of people don't know this but the current Edge engine is Open Source. look here https://github.com/Microsoft/ChakraCore
Re: Microsoft Edge and open source collaboration
#146I'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).
Don't people follow standards-compliant HTML/CSS/JS and compile to the browser of their choice? How often does a standards-compliant site work on Chrome but not on Firefox, assuming that all the targeted features you want are there?
Re: Microsoft Edge and open source collaboration
#147I'm still shocked that they went the Chromium route here. This would have been their chance to really, well, for lack of a better way of putting it: stick it to Google [0] I think it would have been far, far more impressive to use Quantum ( https://wiki.mozilla.org/Quantum ) or WebKit ( https://webkit.org ), with the added benefit that nw.js is already up and going for the Webkit engine (and likely would have suffice…
One thing that’s worse than Microsoft not adopting a technology is Microsoft adopting a technology.
Historically, they’ve used the “Embrace, Extend, Extinguish” strategy quite often, and maybe that’s what’s happening here. But maybe I’m being overly skeptical/borderline cynical...
Re: Microsoft Edge and open source collaboration
#148I'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).
Don't people follow standards-compliant HTML/CSS/JS and compile to the browser of their choice? How often does a standards-compliant site work on Chrome but not on Firefox, assuming that all the targeted features you want are there?
In reality, none of the browsers are quite standards compliant, and developers don’t know the standards by heart, so they often go with what works on their setup, which usually means Chrome.
Re: Microsoft Edge and open source collaboration
#149Excellent news. Google mostly does not have their own desktop OS to "protect", so they are probably incentivised to make the browser and the apps running in it feel as "native" as possible, with proper access to important local resources when relevant. Considering how Apple is dragging their feet with service worker and offline support on Safari (where they have a monopoly on iOS), this is probably a good thing overa…
> "Google mostly does not have their own desktop OS to "protect""
But they do and they are actually Microsoft's biggest competitor on the desktop:
Re: Microsoft Edge and open source collaboration
#150Man, this sucks. I really wish they had open sourced their new engine and stuck with it. I would have volunteered time porting it to Linux/POSIX as well.
This is probably going to get a bit "rant-ey", it's not directed at you, but at the ecosystem at large (and kind of at myself). Everyone keeps saying this, but nobody is actually doing anything about it. People (myself included) talk about how a monoculture is bad, but we still don't use Edge. We talk about how more competition in the browser space is a good thing, but we still complain when the latest features or se…
[deleted]