Well it's not like AI investment money is coming out of thin air - ultimately normies are buying stuff that AI enhanced companies produce which allows those companies to feed this money to the actual winners/1% that truly benefits. I don't think that it's fair to say that AI has been only negative to the normies, when they need to be the ones willingly feeding the beast with their money for the whole thing to perpetuate.
That said I obviously also see a bunch of negative consequences, and perhaps agree that the negatives outweigh the positives.
Most discussion of using code generation on gamedev forums is taboo. As in, do what you want in the privacy of your own home, but in public, try to have some self-respect as an artist.
I've seen some "devs" livestreaming themselves coding a game using LLMs, and it's not pretty. But that's my opinion of vibecoding in general — it's the tool one uses when they don't want to think too much, which is the furthest path to greatness.
Some random examples off reddit (try to compare the sentiment if it had been posted on Hacker News):
In general, interest in AI-assisted coding is associated with people that have no experience whatsoever and just want to make a game out of thin air without putting in the effort.
While it's true that the packages are first party, .NET still relies on packages to distribute code that's not directly inside the framework. You still probably transiently depend on `Microsoft.Extensions.Hosting.Abstractions ` for example - if the process for publishing this package was compromised, you'd still get owned.
Do you add these into the code or into the review itself? I sometimes write these into the review, but I wonder if it's a useful information that should actually be inside the code that will get lost when the PR is merged
Into the review is what I’m talking about. The diff is often a scattered collection of files missing context, and may have refactors that obscure behavioral changes.
So there is reason to add comments that address a different readers understanding than the code rest.
I've gotten notices from Hetzner for hosting IPFS node, apparently it does some local network discovery by default which looks like a malware when you squint hard enough.
Don't forget that some of the new features are mutually incompatible. For example couple years ago you couldn't use the "new ui system" with the "new input system" even when both were advertised as ready/almost ready
As someone who's learned Vulkan to a fairly deep level over the last two years I've found learning with LLMs invaluable, especially for explaining concepts and the whys behind things.
That said debugging graphics bugs has to be some of the hardest things you can do as they generally manifest as driver crash followed by VK_DEVICE_LOST error. Vibe debugging these inside a 60k vibecoded rust renderer is... just not possible.
Agents can get you the initial boilerplate for setting up most of the resources, but are completely clueless about subtle issues with synchronization, transitions, formats and so on.
That said I obviously also see a bunch of negative consequences, and perhaps agree that the negatives outweigh the positives.
reply