Egregoros

the problem with criticizing the use of LLMs without ever using them, is that you most likely have a blindspot for the advancements made in this field in relative short amount of time. I friend who uses LLMs a lot for refactoring code told me, that you can now do with 8gb of RAM what you needed 256gb for a year ago. I guess there a similar increase in regards to energy consumption. I guess we could end up in a situation where 'vibecoding + some adjustments here and there' is more energy efficient for refactoring codebases than doing it manually.

I remember when i rewrote the r_io api of radare2. The rewrite took me 2 weeks of 4 h each day. Integration took over 6 months with the help of a few other people in the end. The ratio of staring at code while laptop is in idle to actually typing and compiling seems rather inefficient to me.

so a while ago i started developing my own 2d platformer game engine. i recently decided, that i also want slopes and all other sorts of things that don't have a rectangle hitbox. so i need some way to created and represent different geometries for the game. yesterday i created a small tool called shapemk. shapemk is a rather simplistic tool: mouse buttons are exclusivly used to create and delete points, the keyboard is used to switch modes and quit-save the program, it must be launched with the dst-path as parameter. It is the anti-thesis to so called "user friendly" software, and it is great. it's not finished yet, but 95% done.