Then they decided to hop on the Java bandwagon, and rewrote their whole UI using some kind of cross-platform Java GUI toolkit. App startup time went from like a tenth of a second to like 30 seconds (at least, that was my subjective impression at the time). Every part of the GUI was laggy and glitchy, it crashed regularly, the documentation was reorganized and much more confusing, etc.
The big-ticket feature additions which supposedly justified the rewrite were some gimmicky stuff for writing formulas in a more standard-math-typography way instead of as plain text, plus some related handwriting recognition thingy, but this ended up being slow, confusing, and ineffective, and cluttering up the rest of the interface.
I still use Maple mainly because of familiarity. I've been using it since the 90s. I'm a contributor to SymPy, but even then I can think through the problem quicker using Maple.
This was before I learned "real" programming, so I actually stuck with the Java GUI to get the pretty-printed math formula editor. Still, maybe that experience caused me to avoid writing Java programs later on...
- No setting of the platform's L&F
- Everything is done on the main thread
- No care is taken about how to write GC friendly code and data structures
- No attention to eye candy
It is like having Assembly developers cry at the shitty performance of C compilers in the early 80's and blame the language.
I subscribed to their online offering when it originally came out, but immediately canceled because the UI is just so far behind its desktop competitors, like Maple, and even Matlab. I want to support this software, it has great potential, but they need to sit down and really rethink how it's put together and delivered to the user.