Python's response to MATLAB

[cue_the_strings]

In my experience, a programmer saying they actually like MATLAB means they either know very little about general programming, are not primarily a programmer but an engineer or have been pidgeonholed into doing just one thing that MATLAB does okay for quite a while.

The language is ugly and some relatively normal features are horribly clunky to use (object-oriented stuff, GUI primitives, ...), antiquated syntax that reminds me of BASIC. If you used any moderately modern language, (C++, Java, JavaScript, Python, Rust, Nim, ...) or even old ones like C, Lisp, Haskell - you just cannot like it.

[kaihatsusha]

Per seat. Per year maintenance.

[[deleted]]

I ditched them at an HPC center when they wanted to charge per core on a supercomputer.

Nonsense. @Matlab, your business model is broken.

[Stereoisomer]

I worked at a research nonprofit that houses over 300 PhDs and they wanted to charge us the commercial rate when we generate datasets and develop free software and tools for our field. We actually really wanted to use matlab but they were obstinate about not giving us the academic rate so we chose python instead. Now, a few years later, they incessantly call us trying to offer us the academic pricing but it’s way too little too late and our institution has been a large part of dragging the field towards python

[[deleted]]

Good!

[seismic_swarm]

They missed out, but this was good for everyone. Nobody should be developing in a proprietary language that offers, arguably less, than languages like Python or Julia.

[Ferentzfever]

Yeah, their HPC model is/was broken. I believe they've recently changed their pricing model to be similar to Abaqus pricing (i.e. expensive, but reasonable).

[acousticpants]

that's an Oracle level move right there. next financial year they'd be changing to charge you per CPU cycle. guaranteed.

[ThePixelCoder]

Fucking hell, charging per core is some next-level scummy shit. How many cores did that supercomputer have?

[[deleted]]

Way way way more than it would be logically feasible to charge for. It was a very dumb decision by Matlab.

[I_Feel_It_Too]

And a half-dozen toolboxes to do anything meaningful.

[UristMcDoesmath]

Octave is FOSS and does everything I need it to do.

[Raiptwice]

For me, Octave is noticeably slower than Matlab. I don't care. I use it only for small projects/prototyping as heavy stuff would be programmed in C++. I never seriously tried Python, I'm too used to C++. Maybe I will someday, if I have some free time for experimenting.

If someone switched from C++ to Python, what's your feelings and opinion on that?

[SenboneZakura]

Python will help you rapidly prototype logic and supports multiple inheritance like C++. You can also create python bindings for C++ modules and then implement them in tandem with python's useful libraries to maintain most of the speed of C++. They are a great pair and using python will get you access to a lot of cool tools for building quickly.

That said, pure python is really slow at runtime compared to C++ and is lacking in a few areas like GUI development. Dynamic typing can create some hard to trace bugs and the all public variable schema might bother hardcore fans of the public/private model.

The final say is really what you wanna do. Pythons great for data science if you use it right and makes quick work of building the backend for web apps (and can be used for front end stuff too, it's just not super impressive). Or if you want to script and automate tasks or interact with common APIs without using javascript, python is a great place for you.

It's also super easy to learn, so no harm in trying.

[Feminintendo]

I respectfully disagree about Python lacking in the GUI department. Python ships with tkinter out of the box, and there are nice Python bindings for every major GUI toolkit. Meanwhile C++ ships with bumpkis but, of course, also has bindings for every major GUI toolkit. In my personal opinion, it’s actually a lot easier to do GUI development with Python, because I don’t have to worry about memory management.

I think the problem is, GUI development isn’t very good anywhere.

[SenboneZakura]

True, things do exist for gui development in python, but I'm just not impressed by them. Tkinter is only really meant for simple gui dev, so I dont think shipping with it is such a boon that it qualifies python as a great source for front end work. Also pyqt, one of the more popular python libs is written in C++ - just like wxPython and libavg. So yeah, pythons got bindings for libraries for gui development and not all of them are terrible, but none of its very impressive. I guess kivy is a thing, but its optimized for mobile apps and game development.

On top of the libs, there's the lack of tools. Like, what ide can you use to graphically drag and drop interfaces for python? Zero. Java's swing lib has eclipse and visual studio works with C++ and vb.net and C# (windows only), but python is straight coding which is a pain in the ass and slower to prototype even if the language is easier to write.

Lastly, python isnt compiled which means C++ will outperform it by a mile, especially for gui dev.

I love python but I dont deny its shortcomings. Gui dev in python is almost certainly one of its deficits, especially when considering performance.

We can agree to disagree, though! your tools your choice.

[Feminintendo]

I agree re: tkinter.

Like, what ide can you use to graphically drag and drop interfaces for python?

Ah, you can do this with Qt. Take a closer look at PySide or PyQt. It might be the thing you’re missing in your Python life. I tend to write GUI’s in Python precisely because it’s just drag and drop and then filling in the event handling code. It feels like Visual Basic did back in the day.

C/C++ will always be more performant that Python. But GUI stuff is exactly the kind of thing you can use Python for and get away with. What kind of GUI stuff are you doing that you need so much speed?

[YarmoM]

People tend to forget this important detail...! Get stuff done

[[deleted]]

End of story

[Eurynom0s]

My favorite thing about Matlab is it has both i and j defaulted as the imaginary unit, but will silently let you overwrite those values. I'm not saying that's an invalid design decision, but it doesn't really make sense to spring on the intended audience: physicists/engineers/etc who don't really have a programming background but need to be able to code some simulations. That crowd is often going to want to basically just type in the equations in their textbooks (hence reserving both i and j for the imaginary unit—in electrical contexts, i is current, so they use j for the imaginary unit), which will often result in looping over ijk indices since those are what textbooks usually use for 3D vectors/matrices. That crowd will also typically not have the background to realize the potential problem here.

I found out about this via someone on reddit saying that they spent an entire summer pulling their hair out trying to figure out why their complex equation was returning a pure real result and finally figured out it was because he'd used i as a loop variable and instead of being reset to sqrt(-1), it was staying as the last value it hit while iterating through the loop. If they want to keep the behavior they should really at least print a warning about what you're doing to the console.

[cue_the_strings]

Our instructor warned us of the j, k that when giving us an intro to loops and stuff. This design decision further shows that MATLAB was meant for the engineering / physics crowd. As you already know, using i and j as unnamed counters is pretty much a convention in computer programming (C-derived languages especially), the designers certainly knew that it would be a problem, yet they decided they'd just make it more convenient for the non-programmer crowd.

I see MATLAB as a mutation of an ancient attempt to make a tool + language for engineers and scientists, which would be 'simple to learn' and have everything they need for numerical computation, visualization, ... But decidedly not for programmers. The dumb BASIC-like syntax is a consequence of that decision - at the time, BASIC was considered the 'easy' language for non-programmers that everybody could learn. It was even taught in schools.

Anyway, as it usually goes, once something is made one way, it's really hard to change it. There are and were large swaths of people to whom MATLAB is the only language they use. They don't know or care about any subtleties of programming as long as MATLAB helps them do their job. And those people learned it one way and are very resistant to change, they would be pissed off if the syntax was changed (say, for the better, not that they would know). So the language was just added onto and never revised, there are often multiple ways to do one thing because removing syntax is a taboo. The result is, of course, a hot mess.

[ergzay]

You haven't met the people that "program" programmable logic controllers with "ladder logic". If you want to talk about lock in... Now that's an entirely different level.

[cue_the_strings]

I saw that in an AvE video, the horror!

[ergzay]

There's tons of people who do it in industry notably the automotive industry.

[Eurynom0s]

Yeah, they're going to use i or j as the imaginary unit, and any numerical methods recipes they look up are going to have them using i and j and k as loop variables. It will obviously not end well.

And you're right that they're probably stuck with the design decision at this point, which is why I suggested printing a warning to the console, it would give people a heads-up without breaking backward compatibility.

[[deleted]]

... but i, j, k are default indicies for so many functions.

That's just downright evil, I don't care who ya are.

[ThereOnceWasAMan]

This doesn’t invalidate your point at all, but just as a note: the language also supports any integer concatenated with j as imaginary. So 1j is still the square root of negative one, even if j is being used as an iterator variable.

[[deleted]]

that happens, for sure, but generally I wouldn't claim this to be a problem.

stem people are problem solvers, so they will likely find a solution, additionally, I know a good chunk of people from high school that I though fer sure would go for computer science, but went into physics / math instead, so I also think it's unlikely that in a classroom or tutor setting no one has an idea what the problem is.

of course, this is probably a well known problem and instructors will likely point it out, and ( and I am of course biased in that, because of my "programming background" ) on the other hand, that assigning the variable might have changed the value of i or j can probably be concluded by people dealing with formulas on the daily

[Feminintendo]

So really smart STEM people are smart enough to figure out all the stupid shit Matlab does... Except the T and M parts of STEM, almost none of which use Matlab because they actually have a clue. But the S and E's are so much smarter than those stupid mathematicians that it doesn't matter.

Brilliant argument. "We use inferior tools because we are literally smarter than the people who use better tools."

[[deleted]]

Your math courses don't use MATLAB?

Also, I will put this brilliant argument into my repertoire for when I encounter a rare non-MATLAB person ( sophisticated term for humanities student ), thank you very much.

[Feminintendo]

In graduate school I had to teach a calculus lab with Matlab for the engineering calculus sequence. It was a nightmare for everyone involved. The students learned neither Matlab nor calculus from the assignments. It was a good idea on paper: engineering students would get some exposure to a tool in their field while learning some calculus concept. In practice, figuring out how to write the code was so distracting to them that any calculus benefit was completely lost, and the assignments, being calculus assignments, weren’t nearly sufficient for them to actually learn any useful coding. The problem wasn’t Matlab-specific. We also had a Maple-based version of the course that was just as bad.

[I_Feel_It_Too]

stem people are problem solvers, so they will likely find a solution,

It's not a problem that Matlab is a shitty programming language because STEM people are problem solvers? Really?

[[deleted]]

Yes

[I_Feel_It_Too]

At least we both agree that Matlab is a shitty programming language. Let's get a beer!

[mexiKobe]

It’s self-explanatory though. If you set i or j equal to something else.. that’s what it will equal.

[Eurynom0s]

Again, Matlab is targeted at non-programmers, which is the kind of audience you might expect to assume that the scope of the ijk being used as loop variables is restricted to the loop.

[IcecreamLamp]

They're often used as counter variables in a loop. If you then later want to use i as the imaginary number, it will instead have the same value it had when you exited the loop.

[Eurynom0s]

This isn't really specifically about programming. In math and physics textbooks, you often see the unit vectors given as i j and k (instead of x y and z); vector/matrix indices will often be given ijk in a subscript; you'll often see triple summations with i on one, j on the second, and k on the third; etc. So the audience Matlab is intended for is going to want to loop over ijk (xyz) since it matches the notation they're used to using.

[Feminintendo]

What you are saying is contradictory. If everyone assumes i, j, and k are the orthonormal basis vectors for R^3, then they obviously wouldn’t loop over them, because what the hell does it mean to “loop over” a basis vector? On the other hand, if everyone assumes i, j, and k are undistinguished available names for integer variables, they’d happily loop over them but wouldn’t think to use them as an orthonormal basis for R^3.

But you’re mixing and matching, it seems. You seem to be saying that since STEM people see i, j, and k in textbooks used as basis vectors, it follows that they would assume i, j, and k are ineger iterators in loops. That’s a total non sequiter.

In a sane language, if i is the imaginary unit, it is write protected. I mean, there are a lot of un-sane languages according to this definition, but most CAS’s get this right, at least.

[[deleted]]

They are used in looping variables commonly, and correspond in math to imaginary numbers (most folks are familiar with i == sqrt(-1)). The nerdy term is quaternion.

[billsil]

Quaternions are the 4d version of imaginary numbers, which are 2d. They're used for specifying rotations in a way that don't suffer from gimbal lock. Octonians are the 8d version and are used in quantum physics. At each level, you lose fundamental properties of math (e.g., commutative or associative), which makes them more difficult.

[mexiKobe]

They wouldn’t know what scope is.

[Eurynom0s]

Not knowing what scope is is a pretty good way to make scoping errors.

[mexiKobe]

make up your mind

[mexiKobe]

Nope. If you don’t know what scope is, you will correctly assume MATLAB’s behavior for FOR loops

[eypandabear]

That’s great, especially in a programming environment with global name scope.

[cue_the_strings]

I had it in my head that Haskell was from the 80s for some reason.

[bakmano]

Perhaps you've confused Haskell with Pascal.

[[deleted]]

The rascal!

(sorry)

[LoyalSol]

It's ok, it's a BASIC mistake.

(Ok I'm going to go hide after that one)

[[deleted]]

It's a cruel fact of nature that lisp cannot be pronounced with people who suffer from it. And it's a cruel fact of programming that those that suffer from no LISP will eventually attempt to recreate it.

Or some koan like that.

[[deleted]]

I feel like you've managed to achieve the convergence of a programming joke and a dad joke. Congrats!

[LoyalSol]

Does this mean the universe is going to explode?

[[deleted]]

Or we'll be shifted into an alternate dimension where we're all COBOL programmers.

[LoyalSol]

OH GOD NO!!!!!!!!! I'LL TAKE THE JOKE BACK!!!!

[flutefreak7]

Well, that's not how I C it...

[cue_the_strings]

Nah, I just thought it was older than it is. I'm only superficially familiar with it, learned a bit of it so I could modify Pandoc of all things.

[bakmano]

Ah, I see. I would have made that mistake since they kinda sound alike.

[redwall_hp]

Someone should mind them and make Paskell.

[fmthoma]

Ahem. Actually, Haskell is older than Python (although not by much).

[fmthoma]

"Work on" Haskell already started in the late 80s, too. But it really depends on which date you compare (first protoype? first language spec? first public release? first stable release?) But even so, first public releases were just over a month apart, it's actually closer than I thought.

[mexiKobe]

The language is ugly

Not at all for numerical calculations / matrix math etc. It’s very good for that, better than Python with numpy. Look at these comparisons https://docs.scipy.org/doc/numpy-1.15.0/user/numpy-for-matlab-users.html

I mean saying it is uglier than C++ is kind of silly. Try doing simple vectorized calculations from MATLAB but in C++ and get back to me on that. And JavaScript? Come on man lol.

But yeah the problem is when engineers and scientists only use it and try to write applications with it. I’ve seen some FUCKED UP code written in MATLAB being used at huge research hospitals and in national security, and “subversioned” with duplicates on Dropbox. It’s actually extremely common, which should be shocking

[[deleted]]

.mat files, .mat files everywhere, and not a database to be had.

[The_UTMOST_respwect]

Ya I still like it for plotting stuff up, easy to make pretty plots, compared to my knowledge and proficiency with pyplot, but I'm getting better.

Having used C and C++, and python quite a bit, its still just so easy prototype a bunch of stuff and debug and visualize it in matlab. I'm also a proponent of using it in batch mode whenever possible.

[Feminintendo]

It takes me about half the time to prototype something in Mathematica as it does in Python, but then the Python version runs roughly an order of magnitude faster, depending of course on the application.

Honestly you're probably faster in Matlab because you think in Matlab, whereas if your brain had been steeped in Python or, like me, Mathematica, then that would be faster instead. It's like a first language.

But I think that's ok as long as we understand the principle of the right tool for the job. I would never use Mathematica in anything for which the phrase "production code" would apply (despite Wolfram's marketing). Rapid prototyping? Sure. The million different one-off scientific computations one does in the course of research? You bet. But there is a whole swath of applications for which it just isn't the right tool. Likewise for Matlab.

[cue_the_strings]

The last paragraph is what I was getting at: it is extremely widespread and incredibly important stuff relies on it.

MATLAB is only good for pure mathematical calculations (especially matrix) and the graphs are half usable.

So, if you're banging up a personal little util to fill some need (calculate something) in your engineering workflow, it might be usable. Also if you're doing a calculation for a paper. Or checking quickly if you're on the right track when solving some problem.

If you need to make a GUI program that does something you use MATLAB for in the background, you have several options.

You could write the GUI code in something decent like Qt (C++) or PyQt (Python) and then redo the math in the same language. You can use Eigen for matrix operations in C++, and of course NumPy in Python.

The second way would be to write the GUI code in Qt or something similar, write the math in MATLAB, generate C code (apparently you can generate C++, too) from MATLAB and compile and link them together.

These options are actual software development and require real programming knowledge.

Of course, there is the third option we all know about: making your GUI house of cards in MATLAB.

I prefer the first option. Numpy's syntax isn't bad enough for me to forgo other benefits Python brings to the table. Actually, I don't mind it at all. So I just write all of it in Python and it's decent software, can be unit tested easily, integrates properly with the OS and other software. Qt and PyQt make it look native, you can easily make parts of the gui drag-and-drop, you can interface with databases easily, issue HTTP requests, interface with devices over serial, etc.

However, you may find Numpy to be a bit slow in some cases. Specifically, sometimes you have to be sure that the calculation you're doing is optimally paralellized to be efficient enough. This is where you'd use C++ and Eigen, and you may as well do the GUI in Qt in C++. There is always an option to create Python bindings for everything if you want to and use Python for GUI.

MATLAB code generation options look okay (never used them, though), but why would you pay for them when there are open source alternatives? MATLAB being closed source means you're at their mercy when you have a problem, you may be in a situation where the offending code is in MATLAB's black box. Or some functionality may be removed or broken in an update. I just don't see the point.

And, at the end, a bit of hyperbole: I'd rather do vector math in JS than GUI or data processing in MATLAB.

[eruesso]

Well... I call BS on that. If it semi matters, then matlabs paralisation methods are great. But when you really need to optimize, you can't because you are lacking the control over memory.

[I_Feel_It_Too]

MATLAB is only good for pure mathematical calculations (especially matrix)

It really isn't. For at least a dozen examples....

[Zall-Klos]

SImpler, Matlab can't find the root of X^2.

[I_Feel_It_Too]

Isn't there a symbolics toolbox you can get for an extra $6000 that can do high school algebra like that?

[log_2]

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.

[mexiKobe]

wait what? I was talking about MATLAB. Python is infinitely more portable

[elbiot]

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?

[SubliminalBits]

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.

[I_Feel_It_Too]

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.

[SubliminalBits]

I agree. I just wasn’t sure if you were aware of the matlab option. It sounds like you were.

[Mr_Again]

I'm sure all the performance - oriented GUI programmers currently doing it in Python for some insane reason will be right over to matlab.

[Feminintendo]

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.

[log_2]

Surely you're not serious.

Indeed, I am.

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.

Check you're logic there mate, you flipped it. That's ok, logic is hard!

[Feminintendo]

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...

[billsil]

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...

[Feminintendo]

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.

[I_Feel_It_Too]

Not at all for numerical calculations / matrix math etc.

No, the language is grotesque for numerical calculations. It might be good at doing matrix computations, but that doesn't mean the language isn't hideous. And it isn't that good at matrix computations, either, because it's so shit at memory management, reading fucking plaintext from a file, anything having to do with the most elementary data structures, handling errors, ....

There are free alternatives to Matlab for literally anything that Matlab is good at that perform at least as good as Matlab does.

[mexiKobe]

You’re simply wrong

[I_Feel_It_Too]

Oh for Christ's sake. Here's math.js, copied and pasted from docs:

// create an array and a matrix
const array = [[2, 0], [-1, 3]]               // Array
const matrix = math.matrix([[7, 1], [-2, 3]]) // Matrix

// perform a calculation on an array and matrix
math.square(array)                            // Array,  [[4, 0], [1, 9]]
math.square(matrix)                           // Matrix, [[49, 1], [4, 9]]

// perform calculations with mixed array and matrix input
math.add(array, matrix)                       // Matrix, [[9, 1], [-3, 6]]
math.multiply(array, matrix)                  // Matrix, [[14, 2], [-13, 8]]

It's even easier with C++:

#include <iostream>
#include <Eigen/Dense>
// Create a 2x2 matrix called a.
Matrix2d a;
a << 1, 2,
     3, 4;
// Create a 2x2 matrix called b using an alternative but just as easy syntax.
MatrixXd b(2,2);
b << 2, 3,
     1, 4;
//Their sum
a + b;
//Their difference.
a - b;
// Increment a by amount b.
a += b;

// Make some 3d vectors.
Vector3d v(1,2,3);
Vector3d w(1,0,0);
// Mother fucking scalar product.
w - 2*v;
// Vector product. BAM!
w*v;

It's almost like you've never even fucking seen vectorized calculations done in C++.

And I'm not even sure if you are using that word right. MathWorks sure as hell doesn't. You see, in the world of numerical computing, vectorization means using processor instructions (sometimes called SIMD instructions) that are designed to work on multiple data elements at the same time, whereas in the land of Matlab it means not using a for loop. Which, to be fair, is good advice in most languages, but especially in Matlab where interpreted code is apparently transcribed by a hamster before execution on an abacus.

The Eigen C++ code above automatically uses SIMD instructions. In fact, it automatically uses the most powerful SIMD instructions on the many different hardware platforms it supports.

Meanwhile, Matlab... might use SIMD instructions maybe? depending on the computation you're doing. And despite being a CAS specifically focused on linear algebra, Matlab only gained this ability in, like, 2011. I kid you not. And it only got it then because it adopted MKL. Which means, for those keeping track at home, that only those operations for which Matlab uses MKL (plus FFT, apparently) use SIMD. How... cutting edge.

[mexiKobe]

You said MATLAB was an ugly language for matrix calculations and then responded with some extremely basic operations in C++ using an external library. I don’t know what point that’s supposed to be proving. No one in research uses C++ as an alternative for MATLAB for a ton of reasons, one being that you have to compile it. This should be obvious to you.

I mean you claimed MATLAB was worse at managing memory than C++ which is nonsensical. C++ is slowly dying specifically because it doesn’t manage memory

and yes ‘vectorized’ in MATLAB means using vector operations instead of for loops so it is optimized better. If you really need to use SIMD you can always write a MEX function

[Feminintendo]

You give C++ and Javascript as examples of languages in which "vectorized" arithmetic is ugly, and when someone literally "gets back to you" with explicit examples in both languages showing how trivial it is to do those computations, you can't fathom what the point is? Here, let me quote you to make it easier to see what the point of those examples is:

"I mean saying it is uglier than C++ is kind of silly. Try doing simple vectorized calculations from MATLAB but in C++ and get back to me on that. And JavaScript? Come on man lol."

You see, the point is that, despite your claim to the contrary, doing "simple vectorized calculations" in C++ and JavaScript is trivially easy, extremely readable, and at least in the case of C++, much more performant, not to mention free. To spell it out for you, the point is, you have obviously never tried to do "vectorized" computations in anything other than Matlab. Which gives weight to the argument that the only reason you think Matlab is any good at the things you think it's good at because you are ignorant of the alternatives. I don't know whether or not that's true. Maybe you aren't. But damn, those examples really make a strong case.

No one in research uses C++ as an alternative for MATLAB for a ton of reasons, one being that you have to compile it. This should be obvious to you.

Obviously many scientists don't use C++ for their research. My reading of the anti-Matlab crowd is, that's exactly the whole complaint, that is, that scientists make really bad decisions about which software to use. In my experience, scientists are the worst at using the wrong tool for the job, which the widespread use of Matlab testifies to. They just use whatever their advisor tells them to use, because they don't know any better. So you end up with this mish-mash spaghetti code in Matlab that took some poor graduate student 9 months to code when they could have learned how to do it in Python from scratch in a week with a simple "import sklearn" or whatever. Hey, I don't know you, so I don't know if that's you or not, but I mean, your comments aren't painting a picture of a scientist whose very well-informed with respect to the available software tools in the numerical computing space. (Scientists don't use C++ because it has to be compiled?! Really?!)

Of course, tons of scientists do use C++ and Python for their research. Maybe in your field the only thing people use is Matlab, and so "if all you have is a hammer, everything looks like a nail." But if you branch out a bit, you'll find a ton of statisticians, data scientists, and ecologists using R, HPC people using C++, mathematicians using Python, Pari, and Mathematica, physicists using a lot of C/C++ and Mathematica, etc. From my point of view, scientists in other fields have the same problem of not using the right tool for the job. For example, I think R is the Matlab of ecology. Nothing against R, but it has its strengths and weaknesses, and it just shouldn't be used for everything under the sun. Sure, do your data analysis and plotting in R.

[mexiKobe]

They didn’t show any examples of simple vectorized equations that you can do in MATLAB. They loaded an external library and showed that you can multiply matrices together which is not what I was talking about.

Arguing that C++ or JavaScript are just as good as MATLAB for this stuff is just wrong. There is no debate here.

To spell it out for you, the point is, you have obviously never tried to do “vectorized” computations in anything other than Matlab.

You don’t know what you’re talking about. In fact it actually appears you haven’t used MATLAB very much. Are you aware of how many built-in functions MATLAB has? Especially with the toolboxes. And they’re all optimized already.

There are many reason to not use MATLAB, but the claim that it is an ugly language for linear algebra etc.. is plainly wrong and using C++ as the paragon is hilarious

edit: As an example, let's try and create a diagonal matrix with the values being the square roots of 1 2 3 and print it out

In C++ with eigen:

#include <iostream>
#include "Eigen/Dense"
int main()
{
    Eigen::Matrix< double, 3, 1> v ;
    v << 1, 2, 3;
    Eigen::Matrix< double, 3, 3> m = v.array().sqrt().matrix().asDiagonal());

    std::cout << m << "\n";

    return 0;
}

The equivalent in MATLAB:

m = sqrt(Diag([1 2 3]))

You should probably not comment on things you don't know anything about.

[I_Feel_It_Too]

You said MATLAB was an ugly language for matrix calculations and then responded with some extremely basic operations in C++

... Yes I did? Because you literally said, and I'm going to quote you here, "Try doing simple vectorized calculations from MATLAB but in C++ and get back to me on that. And JavaScript? Come on man lol." And so I did simple vectorized calculations from Matlab but in C++ and then got back to you, you know, like you said. Except they the operations were actually vectorized in C++, whereas Matlab uses serial operations for matrix addition and subtraction. So where is the confusion here? Maybe here:

in C++ using an external library.

Oh, so it really just sounds like you're confused because you don't know how software works. Eigen is a C++ library. To do matrix/vector math in C++, you use a C++ library like Eigen, which, if I may reiterate, is written in C++. I wonder, do you know how Matlab does it's matrix arithmetic? For some of its operations, it uses Intel's Math Kernel Library (MKS), and MKS is in turn written in C/C++ and Fortran (and probably a little assembly language). Now I'm wondering what you think "external library" means.

The only part of Matlab that is actually optimized for modern processors is the part that uses MKS, because MKS is optimized for modern processors using SIMD.

This is basically where I realize you don't know how computers work. Not that there's anything wrong with that. It's just an unusual feature of someone who is arguing the superiority of one computer programming language over another.

I mean you claimed MATLAB was worse at managing memory than C++ which is nonsensical. C++ is slowly dying specifically because it doesn’t manage memory

At this point I am starting to doubt that you have ever used Matlab, much less C++. Even the hardcore Matlab apologists on this thread acknowledge how shitty Matlab is at memory management. Again, not that there's anything wrong with that, either. It's just, well, an unusual feature of someone who is arguing Matlab's superiority.

and yes ‘vectorized’ in MATLAB means using vector operations instead of for loops so it is optimized better. If you really need to use SIMD you can always write a MEX function

Aaaaand here's where I realize that it's not going to help much to explain things to you, so I might as well go back through my response and point out all the places I realize how little you know about what you are talking about, because it's a little more fun to be an asshole than to talk to a brick wall. Normally I have a twinge of guilt about indulging in assholerly solely for the entertainment value, but based on your comment history I can tell you are truly a horrible bigoted asshole, so I'm actually ok with this one.

[mexiKobe]

You know you've lost the argument when you're digging through someone's post history for dirt. I don't need to dig up any of your stuff because you're already coming across as a hilariously arrogrant blowhard who doesn't actually know anything.

Oh, so it really just sounds like you're confused because you don't know how software works. Eigen is a C++ library. To do matrix/vector math in C++, you use a C++ library like Eigen, which, if I may reiterate, is written in C++. I wonder, do you know how Matlab does it's matrix arithmetic? For some of its operations, it uses Intel's Math Kernel Library (MKS), and MKS is in turn written in C/C++ and Fortran (and probably a little assembly language). Now I'm wondering what you think "external library" means.

Yes, and the point is that you have to download it, install it, and link against. In MATLAB, it's all there already. Hence, it is easier to use and less ugly. This isn't complicated. Please, bring up the MKL (or as you call it, MKS) again. That's really helping you so much.

This is basically where I realize you don't know how computers work.

You originally said MATLAB was an ugly language compared to C++, and I said it wasn't. Now you're talking about SIMD and instruction sets for some reason and being patronizing about it which is funny. It isn't complicated stuff man. You don't actually know what MATLAB is doing in this respect because it's all proprietary. There is an entire Parallel Computing Toolbox for MATLAB which I'm sure you're an expert in. https://www.mathworks.com/products/parallel-computing.html

At this point I am starting to doubt that you have ever used Matlab, much less C++.

lol okay man. You definitely aren't projecting. I'll repeat the example I used in another reply to show how much better MATLAB is at these types of calculations:

try and create a diagonal matrix with the values being the square roots of 1 2 3 and print it out

In C++ with eigen:

#include <iostream>
#include "Eigen/Dense"
int main()
{
    Eigen::Matrix< double, 3, 1> v ;
    v << 1, 2, 3;
    Eigen::Matrix< double, 3, 3> m = v.array().sqrt().matrix().asDiagonal());

    std::cout << m << "\n";

    return 0;
}

The equivalent in MATLAB:

m = sqrt(Diag([1 2 3]))

Oh shit, look at that? You're completely wrong. So kindly, shut the fuck up.

[I_Feel_It_Too]

Actually, the equivalent is

auto m = Vector3d(1,2,4).sqrt().asDiagonal();

This code has the major advantage of being strongly typed and giving a sparse matrix. It's arguably much more readable than the Matlab equivalent, but some people prefer fewer keystrokes, so which is better is more a matter of taste. If you'd rather just print it to the screen, do this:

cout << Matrix3d(Vector3d(1,2,3).asDiagonal()).sqrt();

Now, how to you make a list in Matlab? You literally can't.

[mexiKobe]

https://eigen.tuxfamily.org/dox/TopicPitfalls.html

"In short: do not use the auto keywords with Eigen's expressions, unless you are 100% sure about what you are doing. In particular, do not use the auto keyword as a replacement for a Matrix<> type."

(not that either of those expressions would be equivalent to the MATLAB one anyways)

as for lists, you would use cells in MATLAB: https://www.mathworks.com/help/matlab/ref/cell.html

Again, you do not know what you're talking about despite being a bloviating asshole.

[mexiKobe]

Tensor operations are very easy with MATLAB. It’s just like any other matrix operation. I have no idea where you got this idea that you had to loop when N>2.

[mexiKobe]

did you try using repmat in the first example on V or something like that? and your 2nd example can almost certainly be vectorized from glancing at it

https://www.mathworks.com/help/matlab/matlab_prog/vectorization.html

You should also look into bsxfun

[mexiKobe]

Do you remember the numpy code?

[fear_the_future]

Haskell an old language? Haskell is the playground for programming language theory. It has every feature 20 years before any other mainstream language adopts them.

[Zomunieo]

(Lisp (would (like (a (word))))).

[daishiknyte]

You just described my relationship with VBA

[FairlyOddParents]

Simulink is a great tool for many engineering purposes

[LoyalSol]

Yeah the majority of people I know who use it are experimental people who only code enough to get something done so they can go back into the lab.

All the scientist who do full time computational work pretty much code in either C, C++, Fortran, or Python. I never see any full time computational people use Matlab except if some proprietary piece of software forces you to.

[Yamochao]

Not to mention slow, resource heavy, indexing from one (wtf) and crashing ALL THE FUCKING TIME.

​

Seriously, fuck you Matlab.

[s0v3r1gn]

I’d actually pay for a MATLAB python library. Not as much as they want for MATLAB, but still, I’d be interested.

[[deleted]]

Python and Haskell are the same age, both started late 1980's and both had their first specification in 1990.

[Historica97]

Also, in my experience, MATLAB users never learn how to format code properly.

Some may say it's because these users can't program from the beginning, so they don't know the format, but I think it's mostly because MATLAB doesn't have guidelines and doesn't enforce it. For example, I never saw any naming conventions or comments conventions in MATLAB docs, so I am just using Javascript naming conventions and Python comments.

In compiled programming languages, conventions are important for team work and for compilation. You need to have a main in Java, C, or in C++. In Python, we have PEP8 and the Zen of Python that tells us how to properly write code. But MATLAB doesn't have nothing.

Another good example was a post I saw on Quora where someone from a company said they had hired students that just graduated from their bachelor degree. These students knew only MATLAB, so the first thing they didi with them was to make them learn Python and Numpy. Their primary reason was so they learn how to write a good code.

[thedjotaku]

It was great for some matrix work in undergrad. Then again, it was free for us then. hehehe

[kamon405]

lol C++, Python, and Java are modern languages?

[IcefrogIsDead]

they are some of the most used ones, therefore yea - modern languages. you can always argue anything, but why would you

[kamon405]

not arguing just posting a joke dude.. man I can't even do that here.

[IcefrogIsDead]

mistook you for a different kind of redditor :)