I loved the way people were calling it the X Bone from halfway through the release announcement.

You and the rest of the internet, that’s why they shut down that Discord server.

In my experience, badly.

I mean, it got that error in class_5699.method_65313 so it’s not like it isn’t obfuscated at all.

IIRC TRIM commands just tell the SSD that data isn’t needed any more and it can erase that data when it gets around to it.

The SSD might not have actually erased the trimmed data yet. Makes it even more important to turn it off ASAP and send it away to a data recovery specialist if it’s important data.

Note that this isn’t vkd3d-proton, the one people are using for gaming.

Even if it’s a completely valid address and the domain exists, they still might’ve fat fingered the username part. Going to extreme lengths to validate email addresses is pointless, you still have to send an email to it anyway.

Don’t be ridiculous, I’m going to use an open source password manager to fill an IPv6 address for my email server into the DoorDash signin page.

The problem it solves might not be a problem for anybody but Google. They might be trying to build their own OS to put on future devices.

Vulkan was the successor to AMD’s Mantle API from 2013, though. Metal wasn’t first.

They do seem to alternate between making MacOS graphics worse and wondering why nobody’s making games for MacOS.

Management seem to think that desktop Mac has the same market share that iPhone does and keep wondering why throwing their weight around isn’t working.

Not an expert, but I’ll give it a shot. That way someone will speak up to correct me. 🐸

With an AMD GPU on Linux, you’ve got your kernel amdgpu driver which talks to the hardware, loads firmware, etc.

Sitting on top of that is Mesa, which provides an opengl and vulkan driver. Your application talks to the opengl driver which talks to the kernel driver which talks to the hardware.

Windows has it’s own graphics stack, which has video card drivers and DirectX drivers.

Metal is Apple’s proprietary Vulkan knock-off, which seems to exist to force game devs to write games that only run on MacOS. This hasn’t really worked.

Magma seems to be about inserting a layer between the kernel driver and Mesa, so you can use Mesa OpenGL drivers on top of Magma on Windows kernel drivers? That’s not really something most people are looking to do.

port forwarding/firewall issues that most people don’t know how to deal with

This sort of thing makes me want to tear my hair out when I hear “Why bother rolling out IPv6 when IPv4 just WORKS!?”

NAT, port forwarding and the problems they cause are seen as expected, just the way the internet works instead of the dirty hacks they actually are. Most people aren’t old enough to remember the time when everything connected to the internet had a routable IPv4 address.

That… really feels like something hardware should have been doing, but okay.

It generates an answer that looks correct. Actual correctness is accidental. That’s how you wind up with documents with references that don’t exist, it just knows what references look like.

You couldn’t crank your CPU in the olden days, it’d make games run in fast forward.

Nobody wants to deliberately use the wrong compression type when extracting, so modern tar will figure out the compression itself if you just point it at a file. So tar -xf filename works on almost anything. You don’t need to remember which flag to use on a .tar.bz2 file and which one for a .tar.xz file.

It’s apparently the Pentium 1 and older, so those chips were discontinued in 1999. Almost 26 years old.

Ditching i686 could be a problem for people running 32-bit stuff on modern hardware, though. I expect that’ll hang around for a while yet.

“Hey, here’s a useful thing that I recommend to people: <your work>”

It’s basically a compliment