I don't mind mind paying for good tools/software when you are making good use of it. I guess my problem is with these subscription models where your software evaporates when you stop paying. That's rough. As a simple example, I couldn't imagine being on that kind of a model with Excel. We have tools built on Excel covering disciplines from electrical, mechanical, software, optical and acoustics engineering dating back decades. Having Excel disappear would cause serious damage to our business. This means I have zero interest in anything related to an Excel subscription model where the software goes away when you stop paying.
Frankly, I feel the same way about stuff like Gmail for business. We have always hosted our own email (which isn't that difficult) and have archives going back a couple of decades. Full access with a number of email clients, including Outlook, which is what I tend to use.
We'd be happy paying per project, but if course The Mathworks knows that would bring less revenue.
We've actually had a large effort to move towards python which has been successful in preventing unnecessary MATLAB. Holding the cancer at bay.
Re Excel, they are making offline installs increasingly difficult and expensive, and yet their online version can't do many things (like, Solver doesn't exist, you have to licence it separately, which is essentially impossible in a corporate setup).
Gmail at least has Takeout that works. The problem is that going back to Postfix + anti-spam would require using muscles that have atrophied, and I'm sure I'd have to outsource the problem of getting mail delivered anyway.
> Re Excel, they are making offline installs increasingly difficult and expensive, and yet their online version can't do many things
Yes. I had an ugly experience with a customer who insisted on using the Excel online version. It was a mess.
We are trying to avoid creating tools using Excel any more. Same as you with MATLAB, we are shifting as much as possible to Python. We are using an internal Django site to collect all the tools as apps when it makes sense. In some cases it's stuff that connects to laboratory equipment to take measurements, etc. and it might not make sense to tie it to Django.
That said, you'd be surprised the kinds of things we've contorted Django into doing. We built a robotic test and manufacturing system that runs from Django. It was very interesting to figure out how to use the database for journaling and to maintain state. The last thing you want on a system like that is for the machine to lose state for whatever reason. It worked really well. Not sure I'd recommend it. I wanted to see if we could standardize on Django for the UI and data management on custom automation solutions. No verdict yet.
Frankly, I feel the same way about stuff like Gmail for business. We have always hosted our own email (which isn't that difficult) and have archives going back a couple of decades. Full access with a number of email clients, including Outlook, which is what I tend to use.