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

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