Just a small annotation in regards to react-three-fiber
Reliance on package authors
React-three-fiber is a full reconciler. Technically it does not know what threejs is, nor does it depend on a single version. It would work with threejs version 1 as well the latest. I’ve explicitely chosen that route…
addOnemethod would attempt to use
window.setState , which doesn’t exist!
Just wanted to mention a thing here, instead of window the context here is going to be this as classes run in strict mode by default.
I think that Maps are “faster” than regular objects, only because they are actually regular objects keyed by integers (the order rank of insertion), and most accesses are then using the integer indexing that is much faster than string key indexing (which requires a hashing function and management of hash collisions). For that, the regular objects…