A Mathcad user since the mid-1980s (if I recall correctly), for the past few years, I have been increasingly dissatisfied with PTC's handling of bug releases and their support costs. My impression has been of a product that was nearing EOL, notwithstanding the comment that PTC had just purchased it.
I use Mathcad now for the same reason that I began using it so many years ago: its self documenting capabilities.
I use MATLAB and Maple regularly, partly because I must, and partly because they provide different benefits from Mathcad.
Maple is a very strong player in many ways, but V13 just released doesn't address its shortcomings compared to Mathcad. I regularly use MATLAB because it is so easy to code in, and its vector and matrix handling capabilities are superb.
But MATLAB is not a documenting tool, and even though it provides traceability via scripts, they are simply more difficult to read. The scripts are not meant to be read as an engineering document. I recently was approached by a coworker who needed help preparing a document. He was using data and plots from MATLAB, and writing in Latex. He could have done the whole thing much easier in Mathcad and been done with it.
Several coworkers have seen some of the documents that I've produced in Mathcad, and, thinking that I did them in MATLAB, have labeled a whiz with MATLAB. Others have looked over my shoulder as I developed work in Mathcad, and were impressed with the speed and effectiveness of the Mathcad interface.
I've made a substantial effort to move to Maple, but Maple, despite its significant advantage in a powerful UI, has some significant drawbacks in its documenting capabilities. The latest blurbs from Maple tout "advanced users can use the tutorials to learn about document creation," but Ricard's example above is a good challenge that they don't meet, or at least not easily. Formatting a document "your way," not "Maple's way," is difficult. Maple still insists that units come in these funky brackets [[]], and its 4 different math entry modes can be confusing.
OTOH, Maple's ease of working with equations and plotting, for example, irrespective of my dissatisfaction with the finished product, are superior to Mathcad's, and Maple's right-click and find a tool to help solve a problem leave Mathcad in the dust.
In the end, I want to do the work just once, and this is where Mathcad has been historically the winner. If I need a fast programming tool, MATLAB beats Mathcad IMO. If I want intuitive ODE solvers that recognize that I am using dot notation for time drivatives, then I am OOL with Mathcad, but in luck with Maple.
My Maple productivity suffers, as one might expect, from may lack of familiarity with it, and from my familiarity with Mathcad; I frequently use the wrong keystrokes in Maple. But that would be true in reverse were I a long-time Maple user. I recently had to do some work with transfer matrices, and it was far easier to do with Mathcad, and clear for others to see what I did and why.
Rich
http://www.downeastengineering.com/