Airbrake vs. Chrome DevTools

Airbrake is very good at what it does, I don’t really have any criticism at all on that front. It’s less well-suited when bugfixing goes beyond the immediate error and means looking at a lot of context (particularly asynchronous context) like logs.

Incentivized

Chrome DevTools is best for web developers, front end designers and anyone who is developing a website. It's great for SEO optimization to get advice and info on the assets and resources the website uses and how it performs. Also great for checking if your website is mobile friendly. Great for debugging

Incentivized

• Integration with most of languages and frameworks as well support via existing logging configs.
• Aggregations on occurrences which helps to understand and analyse issues better.
• Web UI displays all error related parameters which I never could have figured out in manual debugging.

• 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

• We use Airbrake in conjunction with OpsGenie, but I feel like there could be more room for integration between the two.
• I think it would also be nice if there was a GitHub integration that would comment on recently merged error-prone PRs, currently, we need to dig into the error to find the commit.
• Generally, more integrations would be nice as people often forget about Airbrake when they are stressed out about an issue.

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

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 love to use Airbrake and New Relic in conjunction. New Relic has better metrics and data that you can really dig into (especially for optimizations), but the error part has always been kinda meh. I fee like Airbrake has done an awesome job at this

Chrome DevTools stacks up well against similar browser tools like those offered by Microsoft Edge and Firefox. It has plenty of strengths and while it may not stand out strongly from the crowd amongst its peers it has built a strong user base around it due to its constant improvement and the popularity of the Chrome browser. It is an easy pick for us to lean on for the majority of our front-end development needs.

Incentivized

• Hugely reduced frontend errors in devices we don’t often test: means more conversions and sales
• Lets us know immediately when there is an error: shorter error durations also means higher sales
• Ultimately once we’ve solved all the most common bugs: more time for developers to focus on other things

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