Why do people seem to prefer Chrome's devtools over Firefox's?

Post by oefrha » Sun, Aug 20, 2023, 2:22 PM UTC

nottorp wrote: post #37

oefrha wrote: post #35

Earlier quoted context omitted.

Developing 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.

Perhaps 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.

Post by jitl » Sun, Aug 20, 2023, 2:23 PM UTC

TheMode wrote: post #34

Sakos wrote: post #32

Earlier quoted context omitted.

This isn't how anything works. If you want a better alternative compiler, you build a new compiler. You don't build an entirely new operating system that includes a new compiler. Want a better grep? Make a better grep, not a whole new shell. Forcing everybody to make their own entire browser in order to provide an alternative devtool is ... madness? What does making a devtool have to do with making a browser? Why sho…

It is how it works. What's your suggestion for the fancy devtools API? Beg Google? Making the implementation of the web standard simpler means increasing the options available, meaning more chance of finding a devtools you appreciate and possibly modify. APIs/Standards deprecate. It is not even a question of "if" but "when". Lowering the barrier of entry is much more sustainable than engineering a whole new spec ever…

Post by tambourine_man » Sun, Aug 20, 2023, 2:24 PM UTC

rohansingh wrote: post #26

jwells89 wrote: post #15

Earlier quoted context omitted.

Yep. 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.

That'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 st…

Post by JonathanBeuys » Sun, Aug 20, 2023, 2:27 PM UTC

rascul wrote: post #42

JonathanBeuys wrote: post #6

For 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 wo…

This does it for me: firefox --new-window google.com

Post by politelemon » Sun, Aug 20, 2023, 2:35 PM UTC

pjmlp wrote: post #25

jwells89 wrote: post #22

Earlier quoted context omitted.

I’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.

So 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.