4 ms·
Maple makes me sad. They had an amazingly effective streamlined GUI circa 2000, a native Windows app which launched significantly faster than the built-in Micro
by jacobolus 11y ago
Maple makes me sad. They had an amazingly effective streamlined GUI circa 2000, a native Windows app which launched significantly faster than the built-in Microsoft calculator tool, and then felt like an upgraded terminal-style REPL with all of math at your fingertips. It had capable plotting with nice embedded graphics, great built in documentation with fast search, etc. It was rock solid, I don’t think I crashed it once. As a high school student, it was an amazing tool for me.
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.
- blt 11y agoI used a version of Maple that shipped with both the Java GUI and the native one. It was amazing how much faster the native GUI started and ran. 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...
- pjmlp 11y agoHowever many Java desktop applications are bad, mainly because developers don't care. - 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.
- thearn4 11y agoI had the same experience, using Matlab in college in the early 2000s was great. But the upside of its decline is that it motivated me to pick up a more general systems programming language for scientific computing work.
- tjl 11y agoThe problem I have is that there is at least one Matlab toolbox I haven't been able to find an open source alternative. I use parts of the System Identification toolbox, but the parts I use aren't the parts that are implemented in the Octave one I found. There are tools in it that will do a transfer function estimate and various things with frequencies that I haven't found an alternative. I've bought the text that covers the toolbox and sometime when I have the time, I'll try and implement it.
- tjl 11y agoI use Maple 16 (I haven't bothered buying any of the newer versions) and it has the Java GUI. The GUI is pretty bad, but if you make sure you work in worksheet mode rather than document mode, you get the old style at least. I also turn off the sidebar. I don't find it to be too bad on my Macs. 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.