Devlog 6: Finalizing the metaballs rewrite and updating dependencies after weeks of falling behind
I have finally finished rewriting the metaballs animation! After going on a hiatus due to school and still trying to figure out why one thing broke after another, I had broken free from it. The slightly overheating fans of my laptop deserved better every time I opened my website. I could hardly remember what I had done a while ago, but I knew that, frankly, as much as the metaball animations were cool (or hot, I should say…), it was just as costly: the frame rate and resolution were too high. The main problem: there was too much work per pixel. Stuff was quite literally being computed millions of times. (More changes to be discussed in my ship.)
For the past few days, I think I spent too much time trying to figure out how to reorder classes because I updated all my tools. Some releases came out very recently; Node.js 26 entered LTS literally three days ago. From the start I suspected it had something to do with the versions. Then after a while of searching I found this issue, which was exactly the problem I had. Then, I decided I would downgrade Typescript from v1.x and pin it to 0.14.1 because it’s unsupported. The solution might sound obvious, and frankly it really does when I think about it now, but it was a silent error, which are the worst kinds of issues. Cheers to progress.
Comments 0
No comments yet. Be the first!
Sign in to join the conversation.