There is also ChromeOS and its similar to WebOS and FirefoxOS and runs on low spec notebooks just fine.
There is little performance difference between Android and FirefoxOS, for both you need at least 512MB RAM (memory), so that it works without lags.
Besides, Gecko is still relevant, and will continue to be for quite some time. Mozilla and Google appear to have a good working relationship when it comes to web standards, and new standards are only signed off when at least two browser vendors (or rather, browser engine vendors) implement the proposed functionality.
> "everyone else supports webkit prefixed CSS properties on mobile"
The question is, how often are these directly used? Isn't the common pattern to target modern features without universal support through polyfills and solutions like Babel nowadays?
Which has < 1% marketshare, and is largely ignored by web developers. I didn't say it didn't exist, I said it wasn't relevant. :)
> The question is, how often are these directly used? Isn't the common pattern to target modern features without universal support through polyfills and solutions like Babel nowadays?
Plenty often enough that users refused to use browsers without support for webkit prefixed properties. People who have a clue may well use polyfills and Babel and autoprefixer, but plenty just do copy/paste coding.