Overall Satisfaction with Chrome DevTools
- Inspect front-end code.
- Find and debug issues.
- Apply changes in the browser for testing.
- Test responsive designs at various device resolutions.
- Test page speed and performance.
- Test various network situations (e.g. low/no internet connection).
- Improved screenshot support.
- Improved CSS tools.
- It's free and powerful.
- It allows for faster development.
- It helps catch problems right away.
While Chrome DevTools are very powerful, it's not the easiest thing to use, as there are so many different tools built in. It takes some exploring to discover all the options possible within DevTools, but with a little exploring, the DevTools become a very powerful asset. Accessing the basic HTML and CSS inspection is very easy though, and that's the most common usage for the DevTools.
I'm not entirely sure what to rate the support for DevTools, because I don't have any experience dealing with official customer support for DevTools. I would guess the primary support for DevTools would be in a Chrome forum. Typically if I have a question or issue, I am able to find an answer from doing a quick Google search. It's pretty widely used, so it's not difficult to find answers.
The main tool I've used that compares to Chrome DevTools is the Firefox built-in development tools. The one thing that I know I like better about Firefox is the screenshot support, which has many great features. Firefox even has a special developer edition of their browser specifically made for web developers. I've used several other browsers built off Chrome that also include the Chrome DevTools. I've used the Safari dev tools a bit, but they don't seem to be quite as intuitive and powerful as the ones in Chrome. There is also a Chrome-based browser called Blisk that I have yet to try.