Garuda for me. The reasons are similar; just replace some optimization with some convenience. It’s a bit garish by default but pleasant to use.

Flatpak has its benefits, but there are tradeoffs as well. I think it makes a lot of sense for proprietary software.

For everything else I do prefer native packages since they have fewer issues with interop. The space efficiency isn’t even that important to me; even if space issues should arise, those are relatively easy to work around. But if your password manager can’t talk to your browser because the security model has no solution for safe arbitrary IPC, you’re SOL.

Good point. It’s more of an “allowing them to build nukes” thing than a “teach them to build nukes” one – although the existing nuclear-armed nations could certainly accelerate the heck out of a Ukrainian nuclear program if they wanted.

Neutrality could work if we give Ukraine nuclear weapons and the ability to make more. That’s the only thing other than a military alliance that’ll reliably keep Russia out of the country.

I get the feeling that nuclear proliferation would not be seen as a desirable solution, though.

Hoo boy, you weren’t kidding. I find it amazing how quickly this went from “the kernel team is enforcing sanctions” to an an unfriendly abstract debate about the definition of liberalism. I shouldn’t, really, but I still am.

Aw, c’mon! Who doesn’t enjoy piping ten megabytes of JavaScript through Webpack to achieve those crucial on-scroll effects on an otherwise static page?

Oh yeah, the equation completely changes for the cloud. I’m only familiar with local usage where you can’t easily scale out of your resource constraints (and into budgetary ones). It’s certainly easier to pivot to a different vendor/ecosystem locally.

By the way, AMD does have one additional edge locally: They tend to put more RAM into consumer GPUs at a comparable price point – for example, the 7900 XTX competes with the 4080 on price but has as much memory as a 4090. In systems with one or few GPUs (like a hobbyist mixed-use machine) those few extra gigabytes can make a real difference. Of course this leads to a trade-off between Nvidia’s superior speed and AMD’s superior capacity.

These days ROCm support is more common than a few years ago so you’re no longer entirely dependent on CUDA for machine learning. (Although I wish fewer tools required non-CUDA users to manually install Torch in their venv because the auto-installer assumes CUDA. At least take a parameter or something if you don’t want to implement autodetection.)

Nvidia’s Linux drivers generally are a bit behind AMD’s; e.g. driver versions before 555 tended not to play well with Wayland.

Also, Nvidia’s drivers tend not to give any meaningful information in case of a problem. There’s typically just an error code for “the driver has crashed”, no matter what reason it crashed for.

Personal anecdote for the last one: I had a wonky 4080 and tracing the problem to the card took months because the log (both on Linux and Windows) didn’t contain error information beyond “something bad happened” and the behavior had dozens of possible causes, ranging from “the 4080 is unstable if you use XMP on some mainboards” over “some BIOS setting might need to be changed” and “sometimes the card doesn’t like a specific CPU/PSU/RAM/mainboard” to “it’s a manufacturing defect”.

Sure, manufacturing defects can happen to anyone; I can’t fault Nvidia for that. But the combination of useless logs and 4000-series cards having so many things they can possibly (but rarely) get hung up on made error diagnosis incredibly painful. I finally just bought a 7900 XTX instead. It’s slower but I like the driver better.

Speak for yourself. I’m going to migrate all of my 22-bit RSA keys to a longer key length. And not 24 bits, either, given that they’re probably working on a bigger quantum computer already. I gotta go so long that no computer can ever crack it.

64-bit RSA will surely be secure for the foreseeable future, cost be damned.

Pretty much business as usual. Those things pop up every once in a while, which is why Germany has no shortage of experienced bomb disposal experts.

And yes, the fact that this is perfectly mundane is chilling if you think about it. That’s how intensely bombed areas work for decades. Battlefields don’t turn back to normal when the war is over. And we casually do this all over the world for a large number of usually stupid reasons.

True, although that has happened with F/OSS as well (like with xz or the couple times people put Bitcoin miners into npm packages). In either case it’s a lot less likely than the software simply ceasing to be supported, becoming gradually incompatible with newer systems, and rotting away.

Except, of course, that I can pick up the decade-old corpse of an open source project and try to make it work on modern systems, despite how painful it is to try to get a JavaFX application written for Java 7 and an ancient version of Gradle to even compile with a recent JDK. (And then finally give up and just run the last Windows release with its bundled JRE in Wine. But in theory I could’ve made it work!)

Note that this specifically talks about proprietary platforms. Locally-run proprietary freeware has entirely different potential issues, mostly centered around the developer stopping to maintain it. Locally-run F/OSS has similar issues, actually, but lessened by the fact that someone might later pick up the project and continue it.

Admittedly, platforms are very common these days because the web is an easily accessible cross-platform GUI toolkit SaaS is more easily monetized.

Nope, they just become less predictable. Which is why in some parts of Germany you can’t build as much as a garden shed without having EOD check the land first. In the more heavily-bombed areas it’s not unusual to hear on the radio that you’re to avoid downtown today between 10 and 12 because they’re disarming a 500-pound bomb they found during roadwork.

And yes, the fact that an unstable bomb capable of trashing a city block is mundane nicely illustrates war’s potential to fuck things up for generations.

Japan might want to get that land under and around the airport checked. There might be some other surprises hidden down there.

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?

Oh, right. Fast Boot. I forgot about that bundle of joy.

But that’s wasn’t the only instance of an NTFS volume suddenly being broken. Another favorite was when I shrunk a volume on one disk from Linux (and then remembered that Windows correspond done it better) and rebooted to have it fixed and Windows proceeded to repair one on a different disk.

NTFS feels rock solid if you use only Windows and extremely janky if you dual-boot. Linux currently can’t really fix NTFS volumes and thus won’t mount them if they’re inconsistent.

As it happens, they’re inconsistent all the time. I’ve had an NTFS volume become dirty after booting into Windows and then shutting down. Not a problem for Windows but Linux wouldn’t touch the volume until I’d booted into Windows at least once.

I finally decided to use a storage upgrade to move most drives to Btrfs save for the Windows system volume and a shared data partition that’s now on ExFAT because it’s good enough for it.

And even if the warheads aren’t functional anymore, nobody wants to get a dirty bomb dropped on their heads. The best nuclear weapon is one that’s not launched.

Still doesn’t mean Russia gets to do what it wants.

I gotta be honest, I haven’t used a dedicated sound card since the Vista/7 era when EAX stopped being a thing and onboard sound could handle 5.1 output just fine. The last one I had was a SoundBlaster Audigy.

These days the main uses for dedicated sound interfaces are for when you need something like XLR in/out and then you’ll probably go with something USB.