Chrome DevTools vs. Percepio Tracealyzer

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

This is a perfect tool to debug complex bugs in your system, especially in regards to inter-task communication. It is also a great tool for beginners, as the documentation is accessible and the support given by the company is excellent

• 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

• Great visualization
• Sometimes awkward views (vertical vs horizontal)

• 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

• It's not always easy to include/integrate Tracealyzer in the OS build. It would be nice to have a simple install/plug n play method for our target.
• Sometimes, the .bin files from Tracealyzer don't always work and we don't know why

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

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

While we started using uCOSIII for our simpler microcontroller products, we also use QNX on more complex targets (full microprocessors) and it is a much more complex platform offering event tracing, memory tracing, and performance measures that are extremely good and integrated. More importantly these tools are fully integrated without any code changes. Tracealyzer is not integrated as much into uCOSIII like QNX's tools, debugger, etc. But, going thru the manual work of adding Tracealyzer to the build, it did help us get to a shippable product.

• 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

• Positive: We were able to find some thread priority issues with Tracealyzer.
• Positive: we were able to see timing of events in the sw/hw that we couldn't otherwise see.