4 ms·
FF is my daily driver (since Quantum in '17) but I've found it really just isn't holding up these days: • Profiling functions between Chrome/FF reveals that Ch
by awful_waffle 5y ago
FF is my daily driver (since Quantum in '17) but I've found it really just isn't holding up these days:
• Profiling functions between Chrome/FF reveals that Chrome is frequently considerably faster (usually 60%+)
• During WebGL work I'll often hit blue screens around memory management (this seems to be a relatively recent development)
• Similarly, trying to profile a WebRTC application with video feeds will consistently trigger a blue screen. (I can tell this is from FF, as the browser itself flashes white a few times before the system goes down.)
• Things like the UI changing - while minor - are enough to cause inconvenience, plus the occasional random feature removal (View Image context menu option) indicates that I'm not necessarily the target audience for the browser.
I actually slightly prefer the devtools in FF than Chrome, but there are a number of quirks that have started appearing over the past year or so, ranging from actual bugs to just weird UX.
As I write this, I'm realizing I'd love a browser that's seen more as a devtool than a catch-all web navigator which happens to have a profiler built in.
- cpeterso 5y agoIf WebGL and WebRTC are causing bluescreens, that is probably a GPU driver bug (though I realize that users don't care whose fault a crash is). If you have steps to reproduce, even if not 100% reliable, you can file a Firefox bug in Bugzilla. Mozilla has contacts at Microsoft and can pass along the bug.
- m45t3r 5y agoYeah, no user application should cause a blue screen of death or kernel panic under normal circumstances, unless it is either a bug or they're messing with something from the kernel (but in this last case, you generally need to run the program with high privilege anyway).
- fulafel 5y agoThis is a distant ideal with today's GPU drivers. Browsers go to heroic lengths to rewrite graphics API calls and recompile potentially hostile code originating from WebGL to avoid tipping over crashy GPU drivers. What normally happens with native GPU intensive apps is that devs change their code to work around driver and OS crashes, and if the app becomes popular, GPU vendors will react to frequent crashes from that app with driver fixes.
- CaptainZapp 5y agoThanks. You make a few interesting points. It just doesn't seem to hit me so bad as an average user. I actually liked the UI they implemented in Android. Alas, I seem to be in a minority
- awful_waffle 5y agoI actually quite like the mobile browser, it hasn't really given me any issues yet. The fact it supports add-ons like uBlock is awesome.