Chrome DevTools vs. Progress Telerik Fiddler

Chrome DevTools helps us identify areas to address such as optimising website performance, cross-browser compatibility, and responsive design. We use the Coverage and panel to identify any unused code, which can cause slow loading times, together with the Network panel which is crucial for analysing page load performance and optimising resources.

Incentivized

I am a senior software engineer and I have actively made fiddler a requirement for all of our engineers to have on their laptops by default. I have recommended it to all web developers that I have worked with and contractors that I have worked with as it has saved my mental stability on numerous occasions when trying to show people details of various web requests when working on integrations between different systems This is an absolutely fantastic product that I have used in a technical capacity many, many times and I will always suggest it as a tool when someone is debugging specifically but also for initial development to see how the requests are formed and for sharing responses and requests details so that others can recreate the request that you have sent through right down to the smallest detail

• Provides clear, easy to understand, and actionable intelligence on how the browser is retrieving, parsing and rendering the page.
• Covers a wide gamut of front-end development tasks, from manipulating CSS rules to line-by-line debugging of JavaScript to helpful page and server insights.
• Continuously incorporates new tools and helpful features. With nearly every major Chrome release there is a "What's new" update with at least one or two useful items.

Incentivized

• I think the layout is too complex, it should be simpler and easy to use for an average developer.
• I would like more tools for CSS oriented development like Grid Helpers, Flux containers, CSS animations, etc.
• I would like a better tool for errors, like telling me what to do if I find a JS problem, CSS problem or a wrong redirection.

Incentivized

• The display could potentially become a bit more user-friendly over time, it's pretty easy to follow but for example, I always view the raw request/response information by default and this is not the default selection, being able to choose the default selection would be nice
• Clearer information and options to reduce 'noise' when viewing the requests, there are often a lot of background requests being sent on a computer, you can filter to roughly see what you want and filter out things that you don't want but there are different types of requests and I can't see how to filter between those - possibly a feature but could be made easier to use potentially
• Nothing else to put, this is a fantastic product so there isn't much else to suggest at this stage of using it and I have been using fiddler for years now in my role as a software engineer

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.

Incentivized

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.

Incentivized

I find them pretty much the same, they have the same tools except Firefox doesn't provide the lighthouse functionality. I do prefer firefox's dark theme and colour palette. But I use Chrome Dev tools because of the Light house functionality that analyzes the page load and scores the website on desktop and mobile experience.

Incentivized

• One major positive impact that using Chrome DevTools has on business is the ability to test your page on multiple devices, screen sizes, and user agents. You can do a lot of QA testing from chrome and that saves time.
• Since DevTools is a free product that comes bundled within another free product I don't see any negative impact that derives from its use.

Incentivized

• Overall this tool has sped up the process of integrating with new systems infinitely
• The cost of fiddler everywhere which is what we use specifically is nothing in comparison to the cost of dev time saved when debugging processes
• Being able to send information around so simply to other support teams to show them what responses we are getting along with the request detail have made communications much quicker and saves a lot of time going back and forth discussing what is being done and what the request is being sent