I'm using FF all the time (except on iOS); in fact, right now as I type. I guess the reason I'm using Chromium for videochat and customer/work-related collabora

I'm using FF all the time (except on iOS); in fact, right now as I type. I guess the reason I'm using Chromium for videochat and customer/work-related collaboration is so that I can close Chromium when I'm done for good ;) and continue browsing on FF for the stuff I care about with many windows and tabs open. Also, I can just nuke credentials for customer-related access when I no longer need those. Maybe I'm burnt by having FF experienced getting slower over time with script-heavy pages (memory or resource leaks?) in the past, and don't want to loose my browsing sessions? It's a moot point anyway since I don't consider collaboration/videochat apps part of the web, so in the end why not have "web" developers target Chrome if they absolutely want to depend on Google. It'll always be more work to target multiple browsers, and developers/bosses will always find arguments to reduce the effort and suck that is browser development/testing. For me, that isn't what the (extant) web is about; there's a reason that a browser, like an MP3 player, used to be more like a decoder/media player rather than all things to all people. I found that, with few exceptions, quality of content I care about correlates inversely with the amount of JavaScript crap on a page/app.