> Kats is standing up WebRender in Firefox for Android
I'm guessing "standing" should be "setting"? Anyway, doesn't seem to work just yet for nightly. I enabled in about:config, but get "unavailable by runtime: WebRender not ready for use on non-e10s Android". Also, "WEBRENDER_QUALIFIED: blocked by env: Has battery"
I filtered by e10s and electrolysis in about:config but couldn't find anything
To me it's very common in the tech community. Maybe a transfer from the embedded/sysadmin/DBA side of things, from what I've seen its usage move over time.
I must have written my text poorly, that's what I intended to convey; that in my experience the term's popularity started in the embedded/sysadmin/dba communities and then spread to the wider tech communities. Sorry! :)
To add to this - this means it could be enabled in focus/klar nightlies, except they don't have an about:config page. You can build it from source, though!
It's very early days currently so you're not missing anything, but as it gets more stable I'm sure it'll be easier to try out.
I keep wondering about GeckoView vs Fennec. Surely Fennec already contains something much like GeckoView, so what will the difference be and when will (Nightly) Fennec switch?
GeckoView and Fennec share the same Gecko code, but GeckoView provides an embedding API for other apps and has some runtime differences like enabling e10s (sandboxed content process separate from the app UI). GeckoView-based features (like e10s and WebRender) will eventually be folded back into Fennec.
I'm guessing "standing" should be "setting"? Anyway, doesn't seem to work just yet for nightly. I enabled in about:config, but get "unavailable by runtime: WebRender not ready for use on non-e10s Android". Also, "WEBRENDER_QUALIFIED: blocked by env: Has battery"
I filtered by e10s and electrolysis in about:config but couldn't find anything