I saw a video yesterday about #threejs and how thanks to their agnostic approach to the renderer which is isolated, they were able to add new renderers like the #webgpu one. I was thinking how I don't do that in my library and also how that ship has sailed, if I wanted to do that for a different renderer in the future I wouldn't have any idea of what to do, which is kind of funny.
Meaning, my library is pretty stuck with webgpu, or as the kids say: coupled.
Another cool thing about managing my library is the fact that until I started with it, I found the joy of rethinking, refactoring, remaking parts of the code base in favor of legitimate improvement. In the past I would certainly just destroy everything and start from scratch, which I think is a thing a lot of developers do, me included, just because we don't want to read another dev's code.
Another cool things is that I've learned a lot about js these last few years. I know there's a lot more to learn, but I still recall there first iteration of my library, it was super slow, but it worked! And I thought that maybe something like C# could increase speed. It was basically the same, except the #javascript was slightly faster. The real issue was that I never understood #webgl, but it got fixed with #webgpu which makes a lot more of sense to me than webgl