Suffice it to say that anyone with sufficient mathematical expertise to actually make sense of this stuff, who is going to do anything interesting will want to use concise names. And yes, this will be the first thing that a programmer who doesn't know it will complain about, but it is far from the largest problem that you have to face in using this stuff. And if you work through the actually important barriers to doing useful stuff with this knowledge, you'll probably appreciate concise notation.
There’s no particularly good reason to shorten `norm` to `nrm` except to be cryptic.
Knowing that `mv` means “function that takes two arguments and multiplies the matrix in the first argument by the vector in the second argument” and that `axpb` means “takes three arguments, and multiplies a scalar by a vector and then adds it to another vector” and that `scal` means “takes two arguments and multiplies the scalar first argument by every element of the vector or matrix in the second argument” requires familiarity with BLAS. In general the names are fairly un-systematic. Once you’ve learned them reading code is reasonably straight-forward (albeit much less clear than code written using more explicit syntax like you’d find in Matlab or similar), but writing code is going to require either frequent trips to the docs or some time spent on memorization.
The names are obviously meaningful, they’re just fairly ad-hoc and not guessable a priori.
Furthermore, it's a specialist expert subdomain—the names are already so standard that everybody who needs them already knows them or looks them up in a second. So I don't see "not guessable" as a valid criticism.
xpy uses x and y because x and y could be vectors, but can also be matrices
mm can not be used for vectors, only for matrices.
Of course, the main reason is that these are names used for the last 40+ years in the standard for this type of software, BLAS.
I'm more than willing to memorize some inscrutable names in exchange for this capability.
(This is probably orthogonal to your comment btw )
Any abstraction layer built with the purpose of making it easy to do linear algebra in software should use names that are domain specific to linear algebra. Which will be the short concise names that make sense to those with mathematical expertise, no matter what generalist programmers think of said names.
Besides, the standard way to call eigenvectors/eigenvalues function is ev in LAPACK - sgeev/dgeev.
And even so, we know today it's preferable to have longer but easier to read code than this kind of garbage.
> sgeev/dgeev.
That's just as bad.
On the other hand, you are free to choose libraries that you use. There is surely no shortage of libraries than invent those "proper" names.
Also, regarding your specific example, `eigen` would be ambiguous. Do you mean eigenvalues? Eigenvectors? Eigenfunctions? Eigenspaces?
Those are the standard BLAS names for those things.
Why not call that function eigen-vectors instead of ev?
Some library authors need to be smacked on the head with a programming book and learn how to design sensible API's.
Seriously, Clojure is typically easy on the eyes but this is just garbage:
axpy? mm? dia? nrm2?