3 ms·
I had this problem 2 years ago. All the models were telling me use libraries that hadn't been invented yet. That was annoying back then, but these days that's
by andai 1y ago
I had this problem 2 years ago.
All the models were telling me use libraries that hadn't been invented yet.
That was annoying back then, but these days that's not so much of a problem.
You can write your program and then simply have it invent the library as well, while it's at it! ;)
- razodactyl 1y agoThese days not so much of a problem because the libraries now exist? Haha
- karmajunkie 1y agomostly because of slop-squatting i’d imagine…
- int_19h 1y agoIt's still very much a problem. For one hilarious example, Gemini (2.5; I haven't tried it with 3 yet) only knows about the old Google API for Gemini, not about the new one. So if you give it code written against the new stuff, it will often do things like, "this is definitely wrong, I know this API doesn't have this method, let me fix that".
- joegibbs 1y agoI find Gemini 3 (and Claude 4.5) also only seem to know about the 2024 era of LLMs and will often just randomly rewrite calls to GPT5 to GPT4o, or Claude 4.5 to Claude 3.5 if it happens to find them in a file, regardless of whether I told it to do anything about that or not.