Most people don't find this to happen because the size of projects and the granularity of the expectations are wildly different.

Unless there is absolutely no abstraction, e.g.: with OpenGL being called from random parts of the game, porting is a matter of mostly gluing two interfaces together.

I have worked briefly in the game industry long ago (not in engine teams though) and ended up writing a few engines for myself after leaving, a couple quite complete.

It’s just a hobby like another. I have zero interest in writing a full game on top of it, or even publishing it.

But do you know who NEVER gives me grief about it? People I know who work at Unity or [previous employer] writing AAA engines.

My last monstrosity is a Rust one with zero dependencies other than the std-lib/OS, Metal/DX12/Vulkan, its own physics engine, spatial audio, vm for scripting and other stuff. I will probably do nothing with it other than having updated my skills in a lot of areas.

If you explore Github, you're gonna see thousands of abandoned game engines, compilers for made-up languages. And that has been happening since before the LLM era.

I used to be part of an OS messaging board in the early 2000s and almost everyone had their own OS. A dozen people or so could even run Firefox! I remember (now legend) Terry bothering us to check out LoseThos or GodOS or whatever was its name, but quite a few people had OSs that could do more than that.

Not all software needs to be commercial to be useful, even if it's just for a learning experience. I have learned a lot from those experiments, even if they're not polished.

As opposed to enforcing your worldview with a lack of regulation?

Because that's precisely what's happening, with the advertisement industry enforcing their worldview through lack of compliance.

These banners handle both ePrivacy consent for cookies etc, but also GDPR Art. 6(1)(a) for processing purposes (personalised ads, measurement, audience insights, precise geolocation, even device fingerprinting).

Naturally in a camera meeting with a "don't tell anyone we said that" appended right before.

The marketing people in the meeting were very angry that California was "doing it to them".

> It's important to do a first pass cleaning up and preparing code before unleashing agents onto it

That’s a good idea in general, but the whole point of the rewrite was that Fable wasn’t capable enough of fixing the old codebase which we were using as a reference.

Another problem I had in another project was with having “sample” code purely written for testing being used as the architectural guidance, despite comments and repeated memories asking not to.

In the end, by the way, the solution was to simply blocking access to specific files, in the Claude settings.json.

But still Claude tried to cheat by running ‘cat file.cpp` a few times, so…

My latest experience was towards a C++ to Rust migration and it failed miserably because the existing codebase enforced patterns I didn't want.

Started famously as batteries-included, until people started realizing there's money in dependencies.

I'm not a lot into Python, though. I still write a lot of it, but I don't really read or participate in its community.

Rust and Node have too many deps because you can't make a Patreon or Github Sponsors page for contributions to stdlib.

Go is batteries-included because it was made by Google by people with a salary.

The people writing "thousands of small packages are good" are the people making money from the clout of having made thousands of small packages.