User-agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
That would only help if it's
implemented directly in the JS engine like Typed Arrays are.
Otherwise the cost of a DOM API call would dominate.
Benoit
On 13-03-21 11:21 AM, Florian Bösch wrote:
What would really help where some helper functions
in native code/SIMD/platform optimized that perform basic matrix
operations like inverse, transpose, multiply, determinant etc.
from array buffer to array buffer/view.
On Thu, Mar 21, 2013 at 3:58 PM, Benoit
Jacob <bjacob@mozilla.com>
wrote:
I have been arguing on public-fx that we are better
off without a browser-supported matrix library because
this is best done in JS both from the perspective of
performance (giving it a bit of time for JS toolchains
to solve roadblocks) and from the perspective of
flexibility and not blessing an arbitrary choice of
matrix library over other ones (and a poor one at that).
Benoit
On 13-03-21 07:04 AM, Si Robertson wrote:
I have to say I can not think of any reason for
native matrix objects to be implemented by browser
vendors unless those objects (a) provide a
significant performance gain over custom code, and
(b) are compatible with WebGL.
Matrix operations that work on typed arrays are
very fast already if the code is optimised, and it
is relatively easily to avoid creating new type
arrays when needed.