By this logic we will never have another new library again. Period.
We will never have a substantial API change to an existing library either, since there will be no training data for it.
> By this logic we will never have another new library again
I didn't mean "we'll never have new libraries again".
My point is that if a dev can't use a tool with the help of GPT or Claude, that tool starts off at a disadvantage.
Innovation can still happen. It just has to fight harder for attention now.
> We will never have a substantial API change to an existing library either, since there will be no training data for it.
If an update breaks the LLM's ability to assist, devs might avoid upgrading until the models catch up. It creates a weird lag where the old API is more AI-friendly than the new one, even if the new one is technically better.
Just look at React Router (Remix). It's a pain having to constantly tell the AI which version you're using. Sometimes you spend more time correcting the AI than writing actual code. (https://x.com/rafalwilinski/status/1924155117172838838)
So yeah, changes can happen. But now they need to account for how LLMs will interpret and support them, not just how humans will.
I think we're still suffering from Win32 and stdio in 2025.
The AI we've got (LLMs) are going to homogenize everything. It may be that new libraries never get written, or at least don't become popular, but that's kind of true today. I do think that LLMs will keep newbies from making both horrible and interesting mistakes, and will keep the experienced from making interesting judgements. Everything will look the same. We'll finally get the "consistency" in interfaces we've always said we wanted.
I didn't mean "we'll never have new libraries again".
My point is that if a dev can't use a tool with the help of GPT or Claude, that tool starts off at a disadvantage.
Innovation can still happen. It just has to fight harder for attention now.
> We will never have a substantial API change to an existing library either, since there will be no training data for it.
If an update breaks the LLM's ability to assist, devs might avoid upgrading until the models catch up. It creates a weird lag where the old API is more AI-friendly than the new one, even if the new one is technically better.
Just look at React Router (Remix). It's a pain having to constantly tell the AI which version you're using. Sometimes you spend more time correcting the AI than writing actual code. (https://x.com/rafalwilinski/status/1924155117172838838)
So yeah, changes can happen. But now they need to account for how LLMs will interpret and support them, not just how humans will.