3 ms·

Firefox is great, and since the Quantum release is getting better on each release. My 2 reasons to keep coming back to Chrome for Mac are the battery life and

Firefox is great, and since the Quantum release is getting better on each release. My 2 reasons to keep coming back to Chrome for Mac are the battery life and DevTools. Firefox is very power hungry in macOS, there are a few bugs reported about that (see [1] and related tickets). The best in terms of energy consumption is Safari, but the dev tools are terrible. So each time that I switch my default browser to Firefox or Safari, I end switching back to Chrome a week after for one of those two reasons :( [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1404042 https://bugzilla.mozilla.org/show_bug.cgi?id=1404042

dylan604 7y ago
What differences are you seeing in the two dev tools? I use both browsers, and as far as what I’m using the dev tools for, they both give me the info I’m looking to find.
- diegof79 7y ago
  Feature-wise most of the dev tools are similar across browsers (in particular Firefox and Chome are similar), but the things that keep me coming back to Chrome DevTools are: - Console. Both Safari and Firefox put the input at the bottom so it's like a command line. Chrome puts it at the top, so it feels more like a code editor. It's a small difference, but that combined with auto-complete and the preview of results makes Chrome console better for me. - Editing of CSS properties. Chrome and Firefox are similar in this area, but Safari is terrible (it improved in Safari 12, but it has some interaction annoyances when you edit rules). Since I work doing UX, I do dev mostly for prototyping. Tweaking CSS in the dev tools is something that I do often. - Display of computed CSS properties, Chrome displays the "trail" of a property in the computed view. (Note: I just discovered that Safari added that as an experimental feature in the latest versions). - Source Maps: My experience with source maps was much better in Chrome DevTools. For example, Chrome shows the files mapped by a bundle in the source tree, while Safari shows the bundle and only displays the source map when you hit a breakpoint (if there is a setting for that I couldn't find it). - Accessibility tree is also a great feature of Chrome DevTools. - For small (simple) projects, the ability to link a file system workspace is also great (although useless for projects that use a lot of JS tooling).
  - joombaga 7y ago
    Input is at the top of the console for me in Firefox on macOS.
  - dylan604 7y ago
    Okay, this makes a little more sense, as you seem to be mainly mentioning differences with Safari. I haven't broken into the Safari dev tools just yet, although I have a feeling that is around the corner since I just read that to see what iOS Safari is doing you use the Safari dev tools when connected via cable. And the rabbit hole just goes deeper. It's turtles all the way down I guess.

dylan604 7y ago

What differences are you seeing in the two dev tools? I use both browsers, and as far as what I’m using the dev tools for, they both give me the info I’m looking to find.

diegof79 7y ago
Feature-wise most of the dev tools are similar across browsers (in particular Firefox and Chome are similar), but the things that keep me coming back to Chrome DevTools are: - Console. Both Safari and Firefox put the input at the bottom so it's like a command line. Chrome puts it at the top, so it feels more like a code editor. It's a small difference, but that combined with auto-complete and the preview of results makes Chrome console better for me. - Editing of CSS properties. Chrome and Firefox are similar in this area, but Safari is terrible (it improved in Safari 12, but it has some interaction annoyances when you edit rules). Since I work doing UX, I do dev mostly for prototyping. Tweaking CSS in the dev tools is something that I do often. - Display of computed CSS properties, Chrome displays the "trail" of a property in the computed view. (Note: I just discovered that Safari added that as an experimental feature in the latest versions). - Source Maps: My experience with source maps was much better in Chrome DevTools. For example, Chrome shows the files mapped by a bundle in the source tree, while Safari shows the bundle and only displays the source map when you hit a breakpoint (if there is a setting for that I couldn't find it). - Accessibility tree is also a great feature of Chrome DevTools. - For small (simple) projects, the ability to link a file system workspace is also great (although useless for projects that use a lot of JS tooling).
- joombaga 7y ago
  Input is at the top of the console for me in Firefox on macOS.
- dylan604 7y ago
  Okay, this makes a little more sense, as you seem to be mainly mentioning differences with Safari. I haven't broken into the Safari dev tools just yet, although I have a feeling that is around the corner since I just read that to see what iOS Safari is doing you use the Safari dev tools when connected via cable. And the rabbit hole just goes deeper. It's turtles all the way down I guess.