Why most mobile browsers build on chromium?
Why most mobile browsers build on chromium?
Angel Jenkins
Evan Lee
Monopoly and simply because it's popular.
Elijah King
Firefox mobile is simply shit. Unusable, pile of garbage code that wastes every CPU clock it consumes.
Dominic Lopez
Because it works better than the other options.
Camden Myers
Firefox Focus will moves from Webkit to Gecko. What do you think will make it better or worse?
Grayson Brown
Why would they not? Which part of the Chromium stack would you like them to change?
Dylan Cruz
nothing
Tyler Wright
Because we're inches away from the WHATWG declaring "HTML"5 defunct in favor of Chrome's source tree, once Mozilla completes their transformation into Chrome, finally forcing M$ to throw in the towel as any semblance of standards compliance goes out the window:
>Chrome/Safari (i.e.: Konqueror)
The deceased:
Elijah Sanders
What about servo? Is that viable?
Caleb Barnes
Palememe is working on restoring firefox's old embedding functionality. Except this is like 2-24 months down the road though. Would work to replace chorme/webkit botnet though. As they forked before the pozz got into mozilla's source tree.
Jonathan Morris
I've been using Dolphin on Android (Webkit based) and it works great).
Michael Scott
at least we now have qt5 webkit engine
James Perry
how is it in 2016?
Julian Torres
FUD. Firefox is moving to Servo and adding a bunch of new features.
Jordan Sanchez
Why would they? They can't because iOS doesn't support gecko. They'd have to drop iOS support then.
Because android is optimized for webview (chrome), so it's twice as fast as gecko. However, gecko is superior in every other way and so is firefox.
Chase Collins
Adam Cox
Also;
Henry Hall
A bunch of new features? Or a bunch of new "features"? Hello, ui redesign, pocket, etc.
Angel Barnes
Source on that one?
Dylan Murphy
Fuggin Lightning
Ryder Rogers
make politics, not browser
~mozilla
Christopher Russell
i don't give a shit about free software. i just want functionality
Leo Gomez
No wonder nobody uses firefox anymore.
As botnet as chromium, and while chromium works 10% of the time, firefox doesn't work at all.
Isaiah Green
When you have freedom, you have the freedom to make it as functional or functionless as you desire. If you desire to do nothing but whinge to other people that they're not working for you, then you get exactly what you deserve.
Kevin Watson
Fingers crossed on Servo not turning into another HURD, but my hopes are not high. And in any case, that would only be one more engine.
Not something people are openly declaring, but there's a lot of "well, even if WebKit/Blink were to become a monopoly that pushed nonstandard behaviors, it's free and open source, so it wouldn't be as bad as IE6!" apologia being thrown around whenever the subject comes up, e.g.:
developers.slashdot.org
reddit.com
James Mitchell
When the Firefox team want to try some kind of idea for Firefox, they don't try out that idea with an experimental version of Firefox. What they do is they try it out on Servo. Servo was always designed to be an experimental platform, it will never be intended for use in a proper release of Firefox. So when their new idea is proven viable by successfully working inside Servo, that's the time when they start modifying Firefox to bring in the new idea.
Levi Martinez
A lot of Servo's core ideas, like breaking every speck of the browser into tiny safe threads/fibers that can be decoupled and isolated from each other, are crucial to making a browser that doesn't choke and crash constantly on the steady diet of shitcode webdevs produce. There isn't any possible way that could be retrofitted into Gecko without a ground-up rewrite.
Cooper Nelson
That's correct. XUL and Gecko were originally using a single threaded programming model and had limited security and no sandboxing features. This means all extensions that relied on the XUL platform had limited security and relied upon the single threaded programming model. Improving Firefox's long term as a software platform inherently meant changing the Gecko programming model so that it would feature a multi-threaded programming model and that each tab would work within its own sandbox. Changing that fundamental model fundamentally means that all extensions that depended on that model break their assumptions about how the platform worked. This also means that it would be impossible to be backwards compatible with the XUL system.