News for hackers. Stuff that matters.
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by wiz21c on Sunday October 19, 2025 @03:33PM (#45637183)
"near clone" is a bit exaggerated. As much as I'm a free software zealot, I don't think Octave comes close to matlab yet (provided you do anything a bit more advanced than the practical of some courses)

See https://stackoverflow.com/questions/12084246/differences-bet...

Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by bee_rider on Sunday October 19, 2025 @04:33PM (#45637695)
I don’t think Matlab or Octave are great languages for software engineering. Actually, these languages are like example #1 of the difference between engineering software vs software engineering: they are excellent tools for writing, like, 10-100 line numerical experiments.

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.

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.

Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by ok123456 on Sunday October 19, 2025 @07:09PM (#45638860)
People who use MATLAB use it for the toolboxes.

The language itself is awful.

Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by enriquto on Sunday October 19, 2025 @09:52PM (#45639567)
> The language itself is awful.

As a programming language freak, I must disagree... in what other programming language can you solve a linear system Ax=b in one line

    x = A\b
without any external libraries or imports, just with the base language?

I never used any official matlab "toolbox", but still love the language via the octave interpreter. It's so clean and straightforward!

Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by torrance on Sunday October 19, 2025 @11:00PM (#45639877)
Well, in Julia, for one.
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by ok123456 on Monday October 20, 2025 @12:44AM (#45640240)
Also APL: b ⌹ A
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by almostgotcaught on Sunday October 19, 2025 @09:58PM (#45639592)
> without any external libraries or imports

Why does this matter in the least? Like you must understand that this is a library call right? Like just put `import numpy as np` in your PYTHONSTARTUP and it's the exact same UX in python.

https://docs.python.org/3/using/cmdline.html#envvar-PYTHONST...

Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by anthk on Monday October 20, 2025 @04:22AM (#45641240)
GNU Maxima.

Not a general purpose one, but good enough.

Also, qalc from libqalculate for trivial stuff.

Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by _glass on Monday October 20, 2025 @06:16AM (#45642208)
In Python you can use a library, then it is: x = np.linalg.solve(A, b). But yeah, Octave is nice, because it stays very symbolic.
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by electroly on Monday October 20, 2025 @12:05PM (#45645486)
In R, this is: x <- solve(A, b)
Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by username223 on Sunday October 19, 2025 @10:15PM (#45639663)
Matlab/Octave is great for numerical programs that perform within an order of magnitude of Fortran. If some things aren't fast enough, you can rewrite them in C or Fortran without too much trouble. If you're doing anything other than numerical computing, it's awful, and you should use a different language.

(Source: I did a PhD using a mixture of Octave for numerical stuff, Perl for text-processing and automation, and C++ for the parts that were too slow. Choose the right tool for the job.)

Re:GNU Octave Meets JupyterLite: Compute Anywhere, Anytime by ok123456 on Monday October 20, 2025 @12:53AM (#45640269)
Modern Fortran is better all around. The compiler will check usage based on interface. It has a working and supported module system (unlike C++). A couple of openmp pragmas will parallelize it. Multidimensional dense arrays are first class objects. The compiler can emit code with array bounds checking. Keyword and optional arguments. Standardized C FFI. f2py inter-op with Python/numpy.

Most people encounter large FORTRAN IV or FORTRAN 77 heirloom codes, and assume that's what Fortran is like in 2025.