AI Megathread

  • 🇵🇦 Nuestro primer dominio localizado está en español en kiwifarms.pa. Our first localized domain is on Spanish on kiwifarms.pa.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
I'm not even going to try to list out the number of significant features Opus has added to my engine. Also it made it like 50%+ faster. It's not magic. I knew all the things I needed to do, they were all just incredibly laborious and fiddly. Now Opus can just one-shot most of it.


 
I'm not even going to try to list out the number of significant features Opus has added to my engine. Also it made it like 50%+ faster. It's not magic. I knew all the things I needed to do, they were all just incredibly laborious and fiddly. Now Opus can just one-shot most of it.
AI gamedev? Probably a godsend for artistic types who are good at music and art but refuse to learn2code. Even so, I do think a little bit is lost there, since tuning little things here and there in the code to get a desired effect is a huge part of making a great game, and LLMs often botch the small, hard-to-notice things that give a game the feeling of a labor of love.

Definitely good for rapid prototyping things, though, when you have an idea and want to know if a basic demo is fun.
 
It's not magic. I knew all the things I needed to do, they were all just incredibly laborious and fiddly. Now Opus can just one-shot most of it.
This is the spot I am in at work. I often know exactly what needs to be done. But it is normally extremely tedious and often cannot be scripted.
Even so, I do think a little bit is lost there, since tuning little things here and there in the code to get a desired effect is a huge part of making a great game, and LLMs often botch the small, hard-to-notice things that give a game the feeling of a labor of love.
It is really good at spotting lots of little things and allowing you to iterate quickly. It is more like a power multiplier if you already know what needs to be done.
 
AI assistance works always the best if you outline exactly what and how you want the AI to do things. Then you can tell it to iterate and change something if it's not good. It is an immense timesaver. Since AI got better in the last few years I have a lot of small programs and scripts I could've written myself easily, but just never bothered because of how tedious it would've been. Real QoL stuff. The other day I had it write an actually working ebuild (gentoo) for basiliskII (old Mac emulator) and write two patches
for another software where apparently the combination of USE flags I used weren't really considered by the maintainer and uncovered a bug. I had to do almost nothing for the latter except provide the failed build log and check if the AI's theory what went wrong actually made sense. Again, I could have done this myself and these were trivial problems, but this saved me real, actual time and it just accumulates. I also simply couldn't have done it that fast. In the time it would've taken me to write the command for creating the diff alone the AI already had written the two required patches by itself.

The only real downside (for me personally) is that AI sucks at writing idiomatic lisp. It basically writes python with a lot of parenthesis. You'd think that's because Lisp is probably not a lot in the datasets but somehow the same models are surprisingly good at smalltalk which makes lisp look like a mainstream language. Generally current, bigger models are somehow all really good at smalltalk. Either it's a language that naturally aligns to LLMs somehow or there are some big and secret codebases out there that ended up in the datasets. This is a bit apropos of nothing but I wanted to mention it somewhere because of how odd it is.
 
Generally current, bigger models are somehow all really good at smalltalk. Either it's a language that naturally aligns to LLMs somehow or there are some big and secret codebases out there that ended up in the datasets. This is a bit apropos of nothing but I wanted to mention it somewhere because of how odd it is.
I think this is about transference. Smalltalk is a simple OOP language, whereas LISP is unique and weird. If LLMs can't write good LISP (try prompting them mentioning the issue and telling them to do it the right way), that'd be a sign that they're not as smart as people say.
 
Atrás
Top Abajo