A slight change in direction
When we started the business in 2002 we just wanted to launch a C/C++ memory analysis tool that could do things none of the other memory analysis tools could do. We succeeded. And 12 years later the other C/C++ tools still don’t offer the features that C++ Memory Validator does.
After a while we realised that some of the techniques we had developed for C++ Memory Validator could be used to develop other C++ related tools. This resulted in tools for Code Coverage, Performance Profiling, Thread Analysis and Flow Tracing. The last one is still an experiment – we’ve never been quite sure where to go with it.
Lots of Languages
But when you are first you can’t always predict the way the market with go. With all of the above languages, except possibly Java, the market has resoundingly chosen Linux. Which leaves tools that run on Windows in a precarious position. As for Java, Eclipse and the toolsuite around Eclipse are the dominant tools.
Maintaining all these tools has become a distraction. We have lost sight of where we should be focussing. So we have come to a decision.
C++ and .Net
Effective immediately we are only going to focus on our C/C++ tools and .Net tools. This will allow us to provide better tools, a better experience and better results for the users of our tools.
- C++ Bug Validator
- C++ Coverage Validator
- C++ Memory Validator
- C++ Performance Validator
- C++ Thread Validator
- .Net Coverage Validator
- .Net Memory Validator
- .Net Performance Validator
With the exception of C++ Bug Validator all other beta tool programmes will cease immediately. There will be no more software updates for any beta tool other than C++ Bug Validator.
Of course this will come as a surprise to some of our customers and we’re very sorry about that. But you have to admit when tools have reached the end of their life.
The whole purpose of this change is to allow us to provide a better result for the users of the core tools of our business rather than a not so good result for a larger group of people. Excellence requires focus and that is what we are going to do.
In the future we may re-package some of the retired tools as free tools. But we’re not sure what direction to go with that. It’s not just a case of making them available for download. The most likely tools to make a re-appearance are for Lua, Python and possibly Perl.
Why don’t we open source them? Sorry, we can’t do that. Large parts of these tools are part of the C++ and .Net tools.