3 ms·
That must be why I have 3 dofferent browsers installed in case a website doesn't work on one of them.
by jdironman 8y ago
That must be why I have 3 dofferent browsers installed in case a website doesn't work on one of them.
- acdha 8y agoWhen was the last time you really needed that? I haven’t had to in years, and I work in .gov. The only thing I see is needing to enable Flash and that was awhile ago.
- reaperducer 8y agoI see it frequently in testing. But then, I'm on the web dev side. Sometimes if I see a web site I think might be too ambitious, I'll open it on each of my testing machines in different browsers, and about 70% of the time, my hunch is right, and it either fails on one or more, or the output looks significantly/unusably different.
- acdha 8y agoIt’s interesting because I also do a lot of web development and have really been enjoying being able to develop in Firefox and not need to worry much about things working in Chrome/Safari, with a little care checking caniuse.com for the newest things.
- SmellyGeekBoy 8y agoFirefox-first definitely seems to be the way forward for web developers. We fell into the trap of Chrome-first and ended up having to fix everything for FF and IE, creating a lot of work. Soon discovered that if we just developed for Firefox everything would generally "just work" in the other browsers.
- acdha 8y agoI generally also find the devtools to be better but both Chrome and Firefox have years-old bugs involving source maps, breakpoints, etc. so I end up cycling between the two during any given day.
- Izkata 8y agoLast week. For some reason just over the past month or so, a couple times Google Hangouts has randomly decided it doesn't support Firefox one day, then work fine the next. A bit further back (maybe a year or so?), I've also had issues with Youtube and my bank's website. Both of those seem to have been fixed, though.
- acdha 8y agoThat’s probably just Google’s aversion to paying for QA. I get the same kind of problems in Chrome and their apps which randomly go away after clearing the cache, resetting the app, etc. I suspect the root cause is that most of their developers want to work on cool things rather than fixing the previous round.