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).
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.
On 21 March 2013 10:24, Florian Bösch <firstname.lastname@example.org> wrote:
On Thu, Mar 21, 2013 at 11:19 AM, Kirill Prazdnikov <email@example.com> wrote:
Will it be a helper library or part of WebGL API ?Neither. It would be implemented in the browser, not related to WebGL, and in my opinion, unusable for it.