Hawk@lemmy.dbzer0.com 3 days ago
If you’re using AI in your process, even early in development, it means the game is no longer 100% human made, so stop the bullshit.
Hawk@lemmy.dbzer0.com 3 days ago
If you’re using AI in your process, even early in development, it means the game is no longer 100% human made, so stop the bullshit.
douglasg14b@lemmy.world 3 days ago
Literally every game that’s made today is using AI as part of the development process.
Damn near every Dev has tab completion on in their IDE. Which is AI based.
white_nrdy@programming.dev 3 days ago
What do you mean “tab completion is AI based”? We have had tab completion for years before LLMs were a thing.
douglasg14b@lemmy.world 2 days ago
Apparently meaning from usage cannot be inferred here? Or you’re just being intentionally obtuse?
A not insignificant number of products literally just call it tab completion these days, because tab completion in many products & IDEa is by default predictive completion, which is ML based. And these days, LLM based.
natecox@programming.dev 2 days ago
Tab completion is a table lookup and has been common for like 20 years. There’s no LLM needed.
douglasg14b@lemmy.world 2 days ago
I used the wrong term, but I guess y’all were unable to infer meaning from usage?
Auto tab or w/e it’s called (Some products literally call it tab completion). Visual Studio was doing it around 2018 IIRC, it was ML based, always has been. Modern versions of it are almost entirely LLM based.
natecox@programming.dev 2 days ago
No, it’s not that we were “unable to infer meaning” (gaslight much?), you’re just wrong.
Firstly, tab completion has been around for effectively ever, and way predates whatever VS Code may have been doing. Ctags indexing, for example, has been around since 1992.
Secondly, even if you want to move the goal post by talking about some specific implementation of ML based indexing, ML is not LLM.