This will help push FOSS gaming and community driven self-hosting of gameservers back towards mainstream. And that's a good thing.

To what are you alluding?

I was into climbing and moutaineering in my teens. I clearly remember when climbing an 8k mountain actually meant something and doing it proved you were an experienced hardcore expedition climber. Everest today is such a joke and farce that I'd be embarrassed to brag of even attempt a summit. They should just install a Via Ferratta, stairs and bridges all the way to the summit and be done with it. That would actually make sense, given the state of things we've reached. They have actual traffic effing jams at the summit and the rainbow flank is littered with the dead bodies of dimwitts taken out by Darwin. It's called "rainbow flank" because of all the colored jackets of the dead.

Just build a staircase, ask an obscene fee to pay for it and void all insurance for anyone who goes above 5500 meters. Problem solved.

Basically everyone who lives in the area or studies the climate or hydrology would tell you that you're insane.

More like a once-in-a-millennium event. Though I suspect it's going to be considerably more common going forward.

Deserts have some amount of normal precipitation, too. And when you get a lot less than normal, that's called a drought. Yes, even in a desert.

We do have pretty good data from tree rings. Unless you think the trees came from somewhere else?

I'm part of that 5%+. The thing about gaming on Linux is that I have no time or mood for fussing around with compatibility issues. Steams Proton layer handles quite a few games without trouble. I used to be a GoG only person but since their requirements for Linux versions are very specific and cause trouble on newer versions of Linux I finally installed Steam on Linux a few weeks back. Sure it's quite a performance hog and it keeps you in the dark about wether it's taking so long to launch because it's running some background update thingie and you have to use top to see what's going on, but other than that, the games listed as playable on protondb launch with a simple click. Which is good.

Guess I'm a steam customer now. After, what, 25 years? I remember when Half-Life 2 came out and they tied it to steam to push the first big digital game distribution platform. Guess that was/is a huge success. Provide good value, get my money. I don't mind.

For all I care they deserve it. If they can't or won't run the servers anymore they should at least release the server as freeware and allow for hobbyists to continue hosting the game. This used to be common practice with multiplayer games and we should enforce this practice by law, especially with people paid solid money for their game copies.

Even worse is when they compromise the VPN operators and then monitor your usage until you do something that makes them decide to crack down on you.

People erroneously think of VPNs as privacy protectors. They aren't, not unless you have very good reason to trust whoever is running the server. If you don't, then they're concentrators for likely subversive traffic and its origins.

The solution to this is to join a party and get involved in the decisionmaking. It's a lot easier than you might think, and you can have a lot more influence that you might expect, precisely because not that many people do this.

Meh.

It would undoubtedly be very expensive at first, and therefore only available to the very wealth (probably not ultra-wealthy -- even without automation, caring for such a clone wouldn't be a full-time job, so call it maybe $30k/year -- within the reach of the upper middle class). But competition would drive automation, and we already have most of the techniques required, having developed them to deal with coma patients and the like, but at lower cost because this case would be dealing with a fundamentally healthy body. My guess based on some napkin math is that cost could be driven down as low as $10k per year. Maybe lower.

$10k per year is expensive, sure, but having an immunologically-perfect organ donor could absolutely be worth it for someone making as little as $200k per year.

If the cost could be driven down to $5k per year... then it's in the range where most middle-class Americans could afford it, even if it meant that they'd have to cut back a little somewhere else; maybe drive an older car rather than leasing a new one, or similar.

LibreOffice was considered somewhat outdated and the OnlyOffice codebase more modern with less cruft. While LibreOffice still is considered as a viable alterternative to commercial solutions, FOSS OnlyOffice / Euro-Office is now officially preferred.

I'm just talking about statistical patterns. I know little about Microsoft patches. I abandoned Windows in 2001, right around the time XP was released, and have never looked back.

Not remotely similar to my experience. Granted I'm writing Rust, and the Rust compiler is *really* picky, so by the time the agent gets something that compiles it's a lot closer to correct than in other languages. Particularly if you know how to use the type system to enforce correctness.

Yes, you have to know how to write tests. A few decades of experience helps a lot. I find I actually spend a lot more time focused on the details of APIs and data structures than the details of tests, though. Getting APIs or data structures wrong will cost you down the road.

Also, I suppose it helps a bit that my work is in cryptography (protocols, not algorithms). The great thing about crypto code is that if you get a single bit wrong, it doesn't work at all. If you screw up the business logic just a little bit, you get completely wrong answers. The terrible thing is that if you get a single bit wrong, it doesn't work at all and gives you no clue where your problem might be.

Of course that's just functional correctness. With cryptography, the really hard part is making sure that the implementation is actually secure. The AI can't help much with that. That requires lots of knowledge and lots of experience.

Deep experience is absolutely required. My antennas are quite good after 40 years.

You really have to know what questions to ask, and what answers not to accept. It also helps to know what kinds of errors the LLM makes. It never outright lies, but it will guess rather than look, so you have to know when and how to push it, and how to manage its context window. When stuff starts falling out of the context window the machine starts guessing, approximating, justifying. Sometimes this means you need to make it spawn a bunch of focused subagents each responsible for a small piece of the problem. There are a lot of techniques to learn to maximize the benefit and minimize the errors.

Yeah, I am definitely not doing UI work.

Speak for yourself. I wrote Android's Keymaster implementation in less than a month, and it was about that size, and then re-wrote most of it in a week when it turned out I'd made some core assumptions that Qualcomm couldn't match in their implementation. It was relatively bug-free for a decade -- even when a third-party security research lab spent a month scrutinizing it. They found a handful of things, but nothing serious. I was amazed, especially since I'd seen the reports they turned in on some other code.

That's just one example. In my nearly 40-year career I've had a half dozen crazy-productive weeks like that, and usually when working on particularly-complex bits. If you haven't had that experience, that's unfortunate. It's not something I could do frequently (or would want to), but it's a glorious feeling when you're that deep in the zone.

Changing your upstream repo away from a commercial service like Github to something else like your own upstream takes 20 seconds if you have to look up the command. That M1cr0s0ft would eventually crappify github was just a matter of time.

If you need some web interface thingie for your central Git repo-base, I recommend checking out Gitea.