# operator-overloading matrix/vector has no use-case in javascript

**URL:** <https://es.discourse.group/t/operator-overloading-matrix-vector-has-no-use-case-in-javascript/186>\
**Category:** I have questions\
**Created:** [January 7, 2020, 8:17pm UTC](https://es.discourse.group/t/operator-overloading-matrix-vector-has-no-use-case-in-javascript/186 "2020-01-07T20:17:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kaizhu256](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/kaizhu256/32/342_2.png) [@kaizhu256](https://es.discourse.group/u/kaizhu256)\
**Post date:** [January 7, 2020, 8:17pm UTC](https://es.discourse.group/t/operator-overloading-matrix-vector-has-no-use-case-in-javascript/186/1 "2020-01-07T20:17:26Z")

</div>

since operator-overloading reached stage-1, would like to challenge one of its use-cases.

my experience with linear-algebra in javascript is mostly for high-level api's like svd-decomposition, matrix-minimization-algorithms, etc. in practice, these high-level api's would never use naive matrix/vector operators -- you commonly need to hand-code the for-loops yourself to take into account application-specific nan edge-cases, and malformed web-inputs.
