Microsoft Visual Studio Code vs. Percepio Tracealyzer

Microsoft Visual Studio Code is highly recommended for the development of systems and / or complex applications entrusted to work teams under a specific methodology, and its use is also recommended for the maintenance of previously developed applications.

It is not recommended as a learning environment for developers with little experience as the learning curve would be too high

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

• Very accessible -- it's compatible with all platforms and environments, free to install, and fast to open
• Strong native support for many languages, and very strong extensibility to provide advanced language features
• Git integration is top-notch, often displaying a better history, diff, and merge interface that is otherwise available in version control systems

Incentivized

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

• Lack of button bar like ones found in Visual Studio.
• Lack of integrated help that could link to YouTube, Channel 9, or other Microsoft videos on how to learn about features.
• Integration with Team Foundation Server.
• Would like to see it having some sort of integration into a Web API testing harness.

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

Solid tool that provides everything you need to develop most types of applications. The only reason not a 10 is that if you are doing large distributed teams on Enterprise level, Professional does provide more tools to support that and would be worth the cost.

Incentivized

Looking at our current implementation, Microsoft Visual Studio Code is perfect for writing code and performing debug operations. Integration with SVN repository is easy and changes can be tracked effectively. Microsoft Visual Studio Code supports developers to write code productively using syntax check and easy customization. Microsoft Visual Studio Code also provides support for IntelliSense which prompts suggestions for code completion. It is easy to step through code using interactive debugger to inspect the root cause of error quickly.

Incentivized

Active development means filing a bug on the GitHub repo typically gets you a response within 4 days. There are plugins for almost everything you need, whether it be linting, Vim emulation, even language servers (which I use to code in Scala). There is well-maintained official documentation. The only thing missing is forums. The closest thing is GitHub issues, which typically has the answers but is hard to sift through -- there are currently 78k issues.

Incentivized

[Microsoft] Visual Studio Code beats the competition due to its extensibility. Their robust extensions architecture combined with the plethora of mostly free extensions written by the community can't be beaten. The fact that this tool itself is provided by a world-recognized company, Microsoft, free of charge is phenomenal. The goodwill garnered by them is immeasurable. Other tools I've used were missing features or were just too rigid, too complicated, or too unsophisticated for my liking. The fact that VS Code is easy to mold to my will with the right extensions seals the deal.

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.

• Positive impact on minimizing time wasted by employees with software installation and setup
• Positive impact on reducing spend on software licensing
• Positive impact on minimizing time used to manage different applications for different purposes - this performs all of the functions we need in basic coding

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.