But yeah the problem is when engineers and scientists only use it and try to write applications with it.
That's because there's no good way to write such applications in Python. The deployment of Python GUI programs for deployment to desktops is a complete nightmare. PyInstaller, p2exe, pyfreeze have all attempted it but they either don't work with everything or needs massive amount of trial-and-error configuration which can completely break as soon as some extra (or newer version) package is required.
All Matlab has to do to keep a hold of it's share is improve the GUI, make it faster and nicer looking (like proper layout), and Python will be left in the dust by people currently looking to switch to it from Matlab.
Uh, all those are for distributing to people that don't have python installed. Surely matlab programs can't be distributed to people that don't have matlab installed, right?
You can. Just buy their compiler toolkit and you can build a binary that doesn't require a matlab license to run. Its the usual Matlab caveat of pay Mathworks absurd amounts of money, but it works fine.
Oh, if we're playing that game (which I am ok with), there are Python compilers, too. They work just as "fine" as compiled Matlab, which is to say, there are pros and cons to both.
But yeah the problem is when engineers and scientists only use it and try to write applications with it.
That's because there's no good way to write such applications in Python.
Surely you're not serious.
Python will be left in the dust by people currently looking to switch to it from Matlab.
I have never heard of anyone who has switched to Matlab because they wanted to. The only people I know who are proficient in other languages but who use Matlab do so because of a project lead who doesn't understand the sunken cost fallacy or because there is literally no other tool that does some very specific obscure thing that Matlab does. It is painfully obvious you are not among that group.
I think I am confused because I am having a hard time parsing this sentence:
Python will be left in the dust by people currently looking to switch to it from Matlab.
At any rate, I have a hard time imagining Python being "left in the dust" by anything, and, to reiterate, I don't know anyone who switched to Matlab from Python because they wanted to. My own perception, which I can't really back up with anything, is that to the extent Python will steal people away from Matlab, it won't really make a significant difference to the number of people using Matlab. In other words, Matlabbers gunna Matlab. I mean, I hope I'm wrong...
People switch to Matlab from Python because they're forced to use certain libraries (e.g., signal processing, Simulink, machine learning). My company doesn't like using it, but when it's better, fine...
Yes, that makes sense. But it's a deal with the devil: you get to use that one obscure library that can do what nothing else can, but you have to use a heinous programming language and pay a lot of money.
4
u/log_2 Aug 06 '19
That's because there's no good way to write such applications in Python. The deployment of Python GUI programs for deployment to desktops is a complete nightmare. PyInstaller, p2exe, pyfreeze have all attempted it but they either don't work with everything or needs massive amount of trial-and-error configuration which can completely break as soon as some extra (or newer version) package is required.
All Matlab has to do to keep a hold of it's share is improve the GUI, make it faster and nicer looking (like proper layout), and Python will be left in the dust by people currently looking to switch to it from Matlab.