27 ms·
From a dev perspective it also loosens Google's grip on Chromium, the #1 rendering engine :D Having Microsoft collaborate and diversify that project is a major
by err4nt 7y ago
From a dev perspective it also loosens Google's grip on Chromium, the #1 rendering engine :D Having Microsoft collaborate and diversify that project is a major win for all of us.
I am hoping/wishing that Mozilla will drop gecko development and repackage WebKit - it would be great for them to join forces and pool resources with the #2 engine!
- timw4mail 7y agoNo, absolutely not.
- alunchbox 7y agoIt's not just a drop in replacement and since Firefox quantum the rending engine has felt butter smooth. Overall Firefox personally 'feels' faster than Chrome, just a personal view but I do love Chrome's developer tools. Not sure if there's a way to improve Firefox's developers tools to bring it in line with a similar experience.
- jjoonathan 7y agoIt's such a shame that failing to test on Firefox became acceptable in dev communities right around the time that Quantum happened and Firefox got back into the fight. Just a year of acceleration on Quantum's timeline, or a year of slippage in Chrome's, could have made such a difference.
- Yizahi 7y agoThere is no such thing as Chromium, it is just a Chrome-lite. Nobody took Chromium and made a separate browser with a separate code from what Google pushes in the trunk. All others do is just add or remove whatever Google allows them, while accepting all serious commits coming down from Chrome. Webkit on the other hand had produced truly different engines - Chromium and Safari, developed differently and making different decisions. If Mozilla with switch to Chrome engine it will be yet another Chrome with mods.
- judge2020 7y agoThat's only because all of these alternatives want to benefit from the free labor Google is putting into Chrome. If Microsoft wanted to, they could actually fork the entire project but then they would need to divert a lot of manpower to the effort.
- lolc 7y agoI think that would be a precarious situation for Mozilla. Not to say the current situation is a good one. So I'm sure they're weighing this. But let's assume they switch to Webkit. In itself that is a huge investment. Then either they track whatever Google wants to do with Webkit, or they fork. But once they fork, they're pretty much on their own again. So there was no gain. To profit from Google's dev, they have to track whatever Google does, and maintain patches for their own things that Google doesn't want to merge. In some important ways, they'd be dependent on Google. Their direct competitor.