My game dev channel: https://www.youtube.com/@joshmoronypixels

I've been performance profiling my JavaScript game and getting LLMs to optimise the findings. The results have been spectacularly good, and improved the performance of my game immensely. This is why I think LLMs are simply getting too good at coding to ignore now.

Get weekly content and tips exclusive to my newsletter: https://mobirony.ck.page/4a331b9076 

MY GEAR:
Keyboard: https://adm42.dev/?ref=3
Neovim setup: https://github.com/joshuamorony/lazyvim/
Animations: https://motioncanvas.io/

#javascript #gamedev #vibecoding 

- More tutorials: https://modernangular.com

Joshua Morony

Using LLMs to optimize JavaScript performance has proven highly effective across 20+ real-world scenarios, reducing turnaround time from hours or days to minutes. The approach involves profiling with DevTools to identify bottlenecks, then having AI analyze and fix the code. Results include transforming a game from 20-30 FPS to near 60 FPS even with 4x CPU slowdown. LLMs successfully handled everything from simple closure optimizations to advanced techniques like baking tile maps into static textures and implementing complex bit-shifting algorithms. While some knowledge transfer is sacrificed, the speed and reliability of AI-driven solutions make them practical for shipping projects without accumulating technical debt.

JavaScript optimisation with LLMs is too good to ignore now

Amen, I really feel this now, when I start to have a codebase! :)

This balance you talked about is something I am also trying to navigate in my own development process. How much should I struggle to make knowledge sticky, and is it worth it? The advance “bit shifting” techniques you talked about were skill sets that separated okay devs and rock star devs. If AI are handling the rock star dev part then what will happen to developers in the future?
Just thinking about this is giving me existential dread.

Unfortunately, AI isn’t the only culprit.
JavaScript is full of unnecessary code.
Easy to get started = easy to write junk code.