Microsoft's Edge browser moving to Chromium
Microsoft's Edge browser moving to Chromium
Posted Dec 10, 2018 9:52 UTC (Mon) by nim-nim (subscriber, #34454)In reply to: Microsoft's Edge browser moving to Chromium by raven667
Parent article: Microsoft's Edge browser moving to Chromium
If they want to have any form of solid independent userbase they need to actually care about other things that cloud giant websites (all the uncool stuff users need that has other applications than watching youtube), they need to take a stance on issues like video codecs and DRM, they need to deliver a browser that protect their users from web and cloud abuses (user data slurpers, trackers, and other antifeatures), they need to care about third-parties that try to embed their web engine in other apps.
If their only compass is “do what Google says is good for the Internet, years late and with new bugs” who is going to care about them? What Google says is good for the Internet is good for Google first, second, and third. With sometimes a few nice side-effects for others to help pass the pill.
Mozilla is rich, astoundingly rich by free software standards, and they've been squandering this money for years on pretty much everything except making Firefox a great browser.
Posted Dec 10, 2018 10:55 UTC (Mon)
by patrick_g (subscriber, #44470)
[Link] (6 responses)
I disagree. What about all the work on the performances? On the Quantum project? On the Servo engine? The Firefox's performances were drastically improved during the last 2-3 years.
Case in point : 2 years ago I created an entry in the bugzilla because I was impacted by a severe slowness when using the search function on my webpage.
At the time here is what I saw when I compared Chrome and Firefox :
Chrome 55.0.2883.87 (on Ubuntu 16.04) : 4 seconds
Now, 2 years later, my bug report is closed because code was pushed into Firefox to solve this performance problem.
Chromium 71.0.3578.80-1 (on Arch Linux) : 4 seconds
Instant result on Firefox instead of the same performance than 2 years ago for Chrome!!!
Posted Dec 10, 2018 20:35 UTC (Mon)
by nim-nim (subscriber, #34454)
[Link] (3 responses)
A browser needs to be performant to stay relevant, but that is not sufficient to shape the web future. It also needs to help people solve new problems. Mozilla is not helping anyone solve new problems today, it is solving the problems Google already decided to tackle (usually successfully) in Chrome.
Posted Dec 11, 2018 12:42 UTC (Tue)
by nix (subscriber, #2304)
[Link] (1 responses)
Posted Dec 12, 2018 10:47 UTC (Wed)
by nim-nim (subscriber, #34454)
[Link]
Posted Dec 14, 2018 11:28 UTC (Fri)
by mgedmin (subscriber, #34497)
[Link]
(There's some javascript for opening/closing report nodes. They work instantly in Firefox, and take several seconds in Chromium.)
Posted Dec 11, 2018 8:34 UTC (Tue)
by k8to (guest, #15413)
[Link] (1 responses)
Let users easily resize badly laid out pages.
There are so many easy wins, but Firefox is not pursuing them.
Heck Firefox/Mozilla *never* addressed the single most popular ever ticket in bugzilla, the request to use external editors for textareas and similar. In fact, they killed the sane solutions for this that grew up in the extensions space.
There's a lot of room to make a better browser for users, and they aren't really trying.
Posted Dec 11, 2018 10:57 UTC (Tue)
by excors (subscriber, #95769)
[Link]
Isn't that basically what Reader View does? (https://blog.mozilla.org/firefox/reader-view/)
> Let users stop [...] autoplay videos.
https://support.mozilla.org/en-US/questions/1222694#answe... says Firefox 63 has new preferences to disable autoplay, and soon they should have proper UI for it.
Posted Dec 17, 2018 4:29 UTC (Mon)
by roc (subscriber, #30627)
[Link] (1 responses)
Mozilla fought Google's proprietary PNaCl (+Pepper) for years, eventually defeating Google and forcing them to adopt Webassembly (which is an evolution of Mozilla's asm.js and much more standards-friendly).
Mozilla took a stance against H.264, unlike Google, but users didn't care, so they had to cave on it after a few years. They contributed a ton of work to AV1 and Opus which are winning the war for free video and audio codecs respectively. Users don't care about DRM either but Mozilla has an easy off-switch for DRM, and a privacy-friendly sandboxed DRM implementation that even downstream Firefox derivatives can use.
Mozilla resisted Google's non-standardized WebP for a long time but is probably going to have to cave on that, because Web developers and users don't care.
Mozilla has resisted supporting the non-standard WebSQL for a long time (and saved themselves a nasty remote code execution bug thanks to that), even though Google and Apple both support it. Not sure if they'll be able to keep resisting it.
Firefox has built-in blocking of tracking scripts that you can easily enable in preferences (Tracking Protection). Firefox nightly blocks third-party cookies. Mozilla is working on blocking more stuff by default.
Faced with the thread of Google taking over the Web, some people choose to focus their complaints on how Mozilla isn't doing everything exactly the way they think it should be done. These armchair generals of course have incompatible ideas about what Mozilla should be doing.
> they've been squandering this money for years on pretty much everything except making Firefox a great browser.
Even during the FirefoxOS era, where this complaint had most merit, Mozilla spent more than $100M a year on making Firefox a great browser.
Posted Dec 22, 2018 5:26 UTC (Sat)
by flussence (guest, #85566)
[Link]
We do care, the length of bug 18574 and the years of campaigning around it leaves no room for doubt there.
But as demonstrated in that bug, Mozilla would rather lead third-party library devs on a death march over 64KB of download size than allow independent open formats to exist on the web.
We don't care much for abusive relationships.
Microsoft's Edge browser moving to Chromium
Link : https://bugzilla.mozilla.org/show_bug.cgi?id=1330375
Firefox 50.1.0 (on Ubuntu 16.04) : 22 seconds
When I do the same search on my webpage :
Firefox 63.0.3-1 (on Arch Linux) : 0 second
Microsoft's Edge browser moving to Chromium
Microsoft's Edge browser moving to Chromium
While Quantum is nice it's basically a "fix the performance gap with Chrome" effort. So while implementation is fresh and performant, it does not showcase any vision for the browser other than "do the same things as Google, years later".
"Write the browser in a better language than C" seems like a vision to me, particularly when they wrote the better language too.
Microsoft's Edge browser moving to Chromium
Microsoft's Edge browser moving to Chromium
Microsoft's Edge browser moving to Chromium
Let users easily fix broken low-contrast designs.
Let users stop carousels (these are on the way out finally) or autoplay videos.
Microsoft's Edge browser moving to Chromium
> Let users easily fix broken low-contrast designs.
Microsoft's Edge browser moving to Chromium
Microsoft's Edge browser moving to Chromium
