![]() I could go on: The MathWorks has many toolboxes for MATLAB, there's Simulink and its related products for which there really is no equivalent in Octave (yes, you'd have to pay for all that. It's also not compatible the other way around! Meaning - code written in Octave often does not work in MATLAB without numerous conversions. How this is better, I really don't see.Īlso, if you learn Octave, there's a lot of syntax allowed in Octave that's not allowed in MATLAB. In my experience, running stuff developed in MATLAB doesn't ever work in one go, except for the really simple, really short stuff - For any sizable function, I always have to translate a lot of stuff before it works in Octave, if not re-write it from scratch. If it tries to be "better", it thus tries to be different, which is not in line with the reasons most people use it for. The idea behind Octave is (or has become, I should say, see comments below) to have an open source alternative to run m-code. This attitude makes Octave lose its purpose completely. This shows that Octave's developers try to make Octave syntax "superior" to MATLAB's. If you read carefully the wiki page you provide, you'll often see sentences like "Octave supports both, while MATLAB requires the first" etc. Rather than provide you with a complete list of differences, I'll give you my view on the matter.
0 Comments
Leave a Reply. |