And I wouldn’t know where to start using it. My problems are often of the “integrate two badly documented company-internal APIs” variety. LLMs can’t do shit about that; they weren’t trained for it.

They’re nice for basic rote work but that’s often not what you deal with in a mature codebase.

Like every time there’s an AI bubble. And like every time changes are that in a few years public interest will wane and current generative AI will fade into the background as a technology that everyone uses but nobody cares about, just like machine translation, speech recognition, fuzzy logic, expert systems…

Even when these technologies get better with time (and machine translation certainly got a lot better since the sixties) they fail to recapture their previous levels of excitement and funding.

We currently overcome what popped the last AI bubbles by throwing an absurd amount of resources at the problem. But at some point we’ll have to admit that doubling the USA’s energy consumption for a year to train the next generation of LLMs in hopes of actually turning a profit this time isn’t sustainable.

Honestly, it’s still the F310 for me. I have mine since the early 2010s and it’s still working perfectly. Those things are built like tanks and between XInput and DirectInput are compatible with just about any PC game of the last forty years, no extra software required. Also, they’re dirt cheap.

Honorable mention to the F710, the wireless version. While Windows 10’s USB stack unfortunately broke compatibility with it (causing randomly dropped inputs), Linux does not have that problem.

It happens on Linux – after your package manager has updated Firefox. Which typically means that you told it to. So it’s not really a surprise.