Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime
by rs186 on Sunday October 19, 2025 @05:32PM
(#45638211)
They are never meant for general software engineer but for numerical analysis/data analysis and engineering. In fact they are quite horrible for writing general software code -- the APIs for IO and HTTP requests are very lacking compared what you can find in other languages, for example.
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime
by duped on Sunday October 19, 2025 @09:13PM
(#45639418)
I haven't found a better CLI calculator utility for writing more than one-liner numerical stuff with some plots than MATLAB and octave. They're fantastic.
Python is trash, by comparison.
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime
by almostgotcaught on Sunday October 19, 2025 @09:54PM
(#45639578)
You think MATLAB is better than (checks notes) a scripting language for writing one liners/throwaway code? Is that what you're saying here? Lol
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime
by viccis on Sunday October 19, 2025 @11:25PM
(#45639958)
>a scripting language for writing one liners/throwaway code
Just objectively not an accurate description of Python
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime
by duped on Monday October 20, 2025 @10:49AM
(#45644577)
1000% yes, because this kind of stuff is not oneliners and you don't want to throw it away.
You also don't have the rats nest that is python environment and package management.
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime
by DarmokJalad1701 on Sunday October 19, 2025 @11:02PM
(#45639886)
> 10-100 line numerical experiments
There's plenty of satellites, rockets, re-entry vehicles whose guidance and control code were designed and written using MATLAB/Simulink and then "autocoded" to C using "MATLAB Coder".
While not my preferred way of doing things, it is popular for this purpose throughout the aerospace industry.
Anyone who runs up against a limitation of Octave has probably hit the point where they should consider switching, but not to Matlab or some other scripting language, but to Fortran or maybe Julia or something.
Therefore, I disagree with the accepted answer in that StackOverflow thread. The language is only good in the first place for short codes anyway, so fixing any little octave/matlab regionalisms is not a big deal. And, since it is a mathematical experiments, you should understand what every line of code does, so running the code without reading it is not really an option.