6 ms·
Why do people seem to prefer Chrome's devtools over Firefox's?
- EspressoGPT 3y agoI develop, test, and debug on browsers that my users are using, and that ain't Firefox.
- danlindley 3y agoAre you comfortable handing Google the power to dictate the future of the Internet?
- gumballindie 3y agoIt's the customers handing power to google, not the devs.
- tambourine_man 3y agoIt’s both, however, developers have a disproportional amount of power to tip the balance.
- jwells89 3y agoYep. The only reason why Firefox, Safari, and eventually Chrome were able topple IE is because devs started writing predominantly for those browsers. Without that push IE would’ve lived on, because users don’t switch that kind of thing unless they really have to. Devs often also have disproportionate sway over the technical choices of friends and family, which is where Firefox got much of its footing earlier on.
- throwawaysleep 3y agoThat’s because Firefox was better then IE. It felt better to use. It was faster. Firefox has no compelling reason to exist for the average user unless privacy is a really high priority for you.
- rohansingh 3y agoThat's not really how I remember it. I remember everyone switching to Mozilla and Firefox because they had great features around bookmarks, themes, and extensions. Then I remember everyone switching to Chrome because it was so fast to launch. Meanwhile, devs were still targeting IE because it was where the users were. It was totally preferable to develop for Chrome or Firefox, but I recall spending countless hours still getting that stuff to IE, because that's what customers were using. Sure, developers helped speed along adoption, but I think the new browsers ultimately succeeded because they're better products for the customer.
- tambourine_man 3y agoFirefox was a better product because it was faster, had tabs, etc and it generally rendered pages as expected. That, in a large part, was on web developers, making sure the user who took the leap had a good time on arrival.
- zogrodea 3y agoWe can see a common sentiment by developers on this thread that they mostly test on Chrome, because that's where users are. I don't think it's likely many developers put in the effort for making the experience of using Firefox better when Firefox had such few users.
- vladvasiliu 3y agoIt's both, as in a vicious circle. Sometimes "customers" don't really hold that much power. For example, I have to use my YubiKey with AzureAD at work. This is broken on Firefox on Linux, but works on Chrome. I can't just not log on to my work email and such. I would have chosen something else than AzureAD, but here we are. I hate having to use multiple browsers, but I still want to support Firefox and only use chrome whenever I depend on AzureAD and make it a point to complain about it. What good did that do? MS sure doesn't care about it. "Just use windows". Right. I'd argue many "customers" could possibly be convinced to drop Chrome in favor of Firefox, I don't think they care as much as HN posters do about this subject. They just want a thing that works. But if half the sites don't work, for whatever reason, they won't be wrangling two browsers like me. They'll just use Chrome and call it a day. So whose fault is it that sites don't support Firefox? 90% of my colleagues couldn't code to save their lives (it's not their job, granted). And the other 10% will just go for what's quicker / easiest to implement. "Everyone uses chrome? Testing on chrome, it is.".
- pjmlp 3y agoDepends, many devs are too keen in using only Chrome and shipping desktop applications packaged in a Chrome shell, because "writing portable code is soooo hard.". Many of whom only care about Safari, because contrary to Firefox, Apple gets to say Chrome doesn't own their platforms.
- ericfrazier 3y agoThe Firefox foundation is the one who ceded power through poor decisions. Devs don't get to decide what users browse on. All users use chrome today and that's it.
- paulryanrogers 3y agoFirefox had no choice in the matter of Chrome's dominance. Google controls the biggest web properties and has the most money to spend advertising and bundling it. Anti-trust has had no teeth in decades. The web was theirs for the taking.
- nottorp 3y agoOf course, Firefox users may just skip your sites because they don't work in FF...
- ericfrazier 3y agoAll none of them? All none users?
- oefrha 3y agoDeveloping in Chrome doesn’t mean the end result doesn’t work in Firefox. Web standards are there for a reason. I develop in Chrome (by develop I mean the full interactive development cycle) but also check in Firefox and Safari once in a while. This post is explicitly about why people use Chrome’s devtools, so you’re just attacking a strawman.
- nottorp 3y agoPerhaps you should read the comment I'm replying to? Editing to not extend the thread: the comment says they do NOT test on anything than Chrome. You maybe do that, the top comment author doesn't.
- oefrha 3y agoI read it, and it’s exactly what I do — develop, test and debug in Chrome. Then I check the site isn’t broken in Firefox and Safari once in a while. It basically never is.
- zogrodea 3y agoWould you mind spelling the difference a bit more clearly? The comment chain has another comment that the browsers developers actually develop for a specific browser (usually Chrome because larger userbase), and this choice developers make influences which browsers users like to use because websites supposedly work better on that browser. So there seems to be variation in implementing the standards you refer to. I don't know much about browser diversity (Chrome and Firefox give near-identical experiences to me as a user), so I personally don't feel that the argument developers significantly influence users holds much water (of course facts don't care about my feelings which may be wrong). I think the only time I noticed a significant difference as a user was when Firefox didn't implement a certain download API allowing for large downloads like Chrome, and I only encountered that difference in using Mega (the upload service).
- tonetheman 3y agoThis is the correct answer. You look at your stats and put your time where it is needed. I like Firefox but it just not popular. And getting a few more devs to use it will not help.
- tambourine_man 3y agoBrowsers are so similar these days, web standards are so well defined, I see little reason to code Chrome-only sites. Having been through the IEs of the 90s/00s, I feel proud that we managed to scape what seemed an irreversible fate and a sense of responsibility to do whatever I can to help prevent it from happening again.
- pjmlp 3y agoTry to use WebUSB or WebGPU on Firefox.
- jwells89 3y agoI’m not sure about WebGPU, but WebUSB was pushed through by Google without any regard at all for Mozilla’s and Apple’s concerns, so it’s not too surprising it’s a Chrome exclusive.
- pjmlp 3y agoSo it isn't as well defined as the parent was making it. Thanks to Chrome worshipping, there is no Web anymore, Apple is the only wall preventing Web developers to replace Web with ChromeOS on their CV.
- politelemon 3y agoThat is not true, two harmful environments does not make either one a saviour, they are simply making web development worse.
- pjmlp 3y agoSorry to break it to you, without Apple, Google would have won already. Doesn't matter how good or evil they happen to be. No one cares about Firefox, apparently not even the large majority of HN folks.
- 3y ago
- ericfrazier 3y ago[dead]
- amq 3y agoCan you modify and resend a request in Chrome yet?
- JonathanBeuys 3y agoFor some reason, new Firefox windows can only be launched from the same environment from which the first window has been started. Even the same user who started FF cannot launch a new window from a new shell. That constantly interferes with my workflow. Example: Say firefox has been started from the Destop already and now I want to start a new Firefox window from a root terminal: su desktopuser firefox It does not work. It gives me "Firefox is already running, but is not responding.".
- vagbesfen 3y agoUse --new-instance.
- JonathanBeuys 3y agoGives me the exact same behavior: Firefox is already running, but is not responding. Have you tried it?
- lightlyused 3y agoPerhaps you need a different profile? (Not tested)
- megous 3y agoYeah, same here. Worked fine in the past. https://megous.com/dl/tmp/b82a40ffb92bb11b.png https://megous.com/dl/tmp/b82a40ffb92bb11b.png Console says: [GFX1-]: glxtest: ManageChildProcess failed [GFX1-]: glxtest: libEGL initialize failed [GFX1-]: glxtest: X error, error_code=2, request_code=152, minor_code=3
- Lapha 3y agoI don't mean this as a dig, but I am curious to know what your use case is for launching new browser windows from different environments is. Something along the lines of remote debugging?
- 3y ago
- pojntfx 3y agoOne of the things that FF's devtools are def. lacking is the ability to jump to a CSS variable's declaration. I keep on jumping back to Chrome just to be able to resolve that.
- EspressoGPT 3y agoWhat, this doesn't work in FF?
- abacadaba 3y agoRIP Firebug. Didn't keep a journal to remember the exact features or reasons but I switched after Firebug went away. Also performance mostly. My site is slow, running in debug mode is slow, and using dev tools is slow. Combine all 3 and it makes a difference. Prob some little features to that are in different places. Firefox when I need to edit and resend a request though.
- Izkata 3y agoThere was a particular way firebug put web requests (ajax) into the console tab that I really liked, that helped with seeing the order things occurred that I remember missing when it went away.
- amelius 3y agoWhy isn't there an API for writing devtools, so that we can have some more competition in this space?
- TheMode 3y agoWe need less API/standard, not more. To have more competition in web devtools, we need to simplify the web standard so more browser can appear instead of forcing some new fancy API on our almost monopoly.
- jakelazaroff 3y agoThere’s no way to simplify web standards without breaking existing websites.
- paulryanrogers 3y agoWebsites should be built based on widely accepted standards, not quirks or monoculture 'standards'. When there were legally enforced browser ballots they had to ... and they did.
- jakelazaroff 3y agoWhen I say “web standards”, I mean official W3C standards, and I think we should be actively hostile to corporate attempts to take over that process. But I disagree that we shouldn’t also try to accommodate quirks. That’s why we have `Array.flat` instead of `Array.flatten` — the standards body decided to come up with a slightly atypical name for the feature rather than breaking a bunch of websites.[1] Our collective history is too valuable for us to be breaking stuff just to make engineers’ lives easier. [1] https://developer.chrome.com/blog/smooshgate/ https://developer.chrome.com/blog/smooshgate/
- paulryanrogers 3y ago> we should be actively hostile to corporate attempts to take over that process. Hard agree. I've become convinced their power to ignore, replace, and EEE standards requires legal intervention. So far it seems only randomized browser ballots can effect any meaningful change. Otherwise websites will just build for the dominant browser regardless of any agreements among them.
- smslyng 3y agoMust join the choir and say that eventhough I have been a die hard FF fan, its gotten to the point of an impending divorce if performance doesn’t get better. I find myself switching to chromium more and more often. And then there are the extensions, that I sometimes can’t find for Firefox. That’s a minor annoyance than anything else though. There are also a bunch of things that keeps me with FF. multi container tabs is one of my most loved ones. But I simply don’t get why the Team does make that feature even better. Like making it much easier to distinguish which container tab I am in. And adding even more customisability pr container-type. Regarding DevTools, I really do t think I have a strong preference at all. But the stronger/more consistent performance the DevTools in chromium comes out slightly ahead. For me it’s the overall experience which makes it a close race
- otabdeveloper4 3y agoFirefox has been faster than Chrome for many years now.
- crgwbr 3y agoI don’t think that’s true for devtools. I use FF devtools ever day, and it frequently crashes. Even the view source page has horrible performance issues when using cmd+f.
- seba_dos1 3y agoBecause they're used to it.
- ofrzeta 3y agoWhatever. I just keep using Firefox on Linux, Windows and MacOS for browsing the web and development. Haven't noticed any impediments with the latter. Actually, as alluded in another comment here, I recently learned to modify requests inside FF so I didn't need to start Postman for just a simple test.
- aPoCoMiLogin 3y agocurrently FF has comparable devtools, but back in the day, FF was lacking a lot of features, like websocket inspection which was implemented around 2019 [1] where in chrome you could do that since 2011 via net-internals (i'm unable to find the date when it was implemented in devtools). so I think because of thing like these, the popularity of chrome devtools was just getting bigger and bigger. [1] https://hacks.mozilla.org/2019/10/firefoxs-new-websocket-inspector/ https://hacks.mozilla.org/2019/10/firefoxs-new-websocket-ins...