- From: Joe Pea via GitHub <sysbot+gh@w3.org>
- Date: Sat, 28 Dec 2024 02:11:19 +0000
- To: public-fxtf-archive@w3.org
> especially given that we have no reports of actual problems caused by this I'd wager we don't have very many people using DOMMatrix because other math libraries like those in Three.js and other libs are far more popular. I see only 92 results for "rotateAxisAngleSelf" in JavaScript across GitHub, https://github.com/search?q=rotateAxisAngleSelf++language%3AJavaScript&type=code most of which are unused polyfills, type definitions, or unit tests (and a few instances of my own code 🤣). There are less than a handful actual uses. In contrast, I see 2.8k results for Three.js `makeRotationAxis` across GitHub, https://github.com/search?q=makeRotationAxis+language%3AJavaScript&type=code&l=JavaScript most of which are actual uses of the API. Just the "gl-matrix" library alone has a whopping 17.8k results across all GitHub JavaScript compared to 4.3k for "dommatrix". Many of the "dommatrix" results are polyfills and mock DOMs, as well as irrelevant results like "getRan**domMatrix**", whereas with "gl-matrix" most if not all the results I've seen are actually importing that library. I propose we try to make DOMMatrix be the best math library it can be so that more people can actually adopt it, and fix discrepancies like in this thread's OP. Geometry Interfaces is currently a very limited API, missing a bunch of desirable features that other userland libraries have. -- GitHub Notification of comment by trusktr Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/275#issuecomment-2564141223 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 28 December 2024 02:11:20 UTC