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.
Depends. On Linux or older macOS where light mode typically means a comfortable light gray? Light mode is the way to go. On Windows where light mode means an eye-searing onslaught of #FFFFFF? Dark mode is the only sensible choice.
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.
And that's why copyright infringement is a crime, just not the same crime as theft.
Most of our plants were already fairly old and major overhauls would've been necessary.
In 2000 we had plans for a nuclear exit already, intending to phase them out until 2015. In 2010 the government decided to keep some running. IIRC they did that in part so they could shut down coal plants instead.
Then Fukushima happened and we went full panic mode, deciding to shut all of them down ASAP. Then the Ukraine war got reignited and the timeline got slightly stretched out a little again for practical reasons.
The last three reactors got shut down last April, about eight years later than the 2000 plan intended.
It's a bit more complicated. We were already planning to get out of nuclear because our plants were aging and new ones weren't economical. Then the government decided to freeze those plans for the time being. (IIRC one reason was that they wanted to close some of our terrible coal power plants first.) Then Fukushima happened and the Greens got everyone to panic.
We could've gone with a measured response but a combination of the Greens believing that nuclear power is infinitely bad and plenty of old people still having vivid memories of fallout-related health warnings from Chernobyl was enough to drive most of the country into an antinuclear frenzy. It's almost a miracle they didn't force all of the plants to scram immediately.
Why not 2.022k?
In my experience rear-mounted sensors are the most accurate, closely followed by under-screen sensors. Side-mounted sensors are utter garbage.
Accuracy isn't even that much of an issue, it's that the side-mounted ones are far too easy to accidentally trigger just by handling the phone. I can't count the number of times my last two phones told me I had three incorrect fingerprint attempts after I had just pulled them out of my pocket.
Then I got a Pixel and I have no more such issues and virtually perfect accuracy. Same on a Samsung tablet. Same on an old phone I had where the power button was on the rear and had a full-size sensor.
Basically, I'm perfectly happy with any front- or rear-mounted full-size sensor. Those tiny side-mounted ones suck.
The Crucial P3 series is QLC-based, which I'm not a huge fan of because your performance is strongly dependent on the SLC cache. (Also, early QLC had endurance issues but no idea if that's still the case.) I'd go with a TLC-based SSD if it doesn't break the budget.
Other than that it looks like a decent build. Should perform well with Linux.
"Well, excuuuuuse me, princess!"
gets shot twice, just to make sure
Hurd?