Modern cars have tens of ECUs, so if you had to have all of them for testing, that would get unwieldy extremely quickly. Not to mention that cars are pretty resilient to having random parts failing, you don't want to lose the entire dashboard just because the ECU that provides camera data failed, or something.

Considering the vast majority of mods are just adding some items or creatures, they don’t need to worry. This won’t be more than the regular API changes in between versions that they’re already used to, unless it’s a more graphics heavy thing like a shader mod.

Also, even with shaders, it’s fairly straight forward to port a shader from OpenGL to Vulkan (for the most part Vulkan just gives more flexibility in that regard). The stuff around it is the hard part.

For now there aren't many popular drivers that use Rust, but there are currently 3 in-development GPU drivers that use it, and I suspect that when those get merged that'll be the real point of no return:

- Asahi Linux's driver for Apple GPUs - https://rust-for-linux.com/apple-agx-gpu-driver

- The Nova GPU driver for NVIDIA GPUs - https://rust-for-linux.com/nova-gpu-driver

- The Tyr GPU driver for Arm Mali GPUs - https://rust-for-linux.com/tyr-gpu-driver

I suspect the first one of those to be actually used in production will be the Tyr driver, especially since Google's part of it and they'll probably want to deploy it on Android, but for the desktop (and server!) Linux use-case, the Nova driver is likely to be the major one.

Then there’s the stupid BIOS warning that requires you to press ESC for the computer to boot if it’s not plugged in to the official charger, which means that if it ever reboots at night it’ll just keep you awake (because the power management hasn’t been initialized yet so it’s stuck at 100% CPU) until you go press ESC.

Oh and it thermal throttles all the time so the CPU performance is good for a few minutes and then it’s just awful.

I’d you’re interested in this, I know systemd has been working pretty hard on getting TPM-provisioned credentials usable on Linux though!

Nowadays, most distros are moving towards having /bin be a symlink to /usr/bin, so it's mattering less and less, but I see no reason not to just do /usr/bin/env which is supposed to be on the same place on every distro.

What would Apple even gain out of this? They don’t have a competitor to MS Teams, FaceTime is hardly targeting the same segment.

The new electron app does take more resources, but at the very least it works.

And I'd vastly prefer it that Google (and Apple, and Amazon, and Home Assistant, and IKEA, and Philips, and...) all agree on the same protocol than each vendor making up its own thing.

It's interesting to me how from his account, everyone is fairly sympathetic to him regarding his charges (he mentions his employer showing up to his interview in a sports jersey in reference to his charges!), and how he mentions he knows several actual sports players used his site. It really goes to show the state of modern streaming.

Matter simplifies this. It defines the API layer. You can use Thread without Matter, at which point you basically have Zigbee + IPv6, but the power comes with Matter since now every device is speaking the same language and can actually understand each other.

Even iPhones have been able to talk to thread devices directly for a while now, so it's a fairly transparent process.

Zigbee is great for communication instead of WiFi, but it’s just one part of the equation - it says nothing about the specific commands a device will respond to. You couldn’t pair a Philips remote with an IKEA lightbulb.

Matter attempts to fix it by actually defining the protocol that these devices use. It’s also fully local and open source, which is great. The actual transport layer can be WiFi, but it can also be Thread, which is a newer standard based off Zigbee, and AFAIK some Zigbee controllers can be reprogrammed to support it.

They don’t specify what transport layer they are using here, but considering the kind of devices they are showing (battery-powered remotes) it’s almost definitely Thread.

It was definitely already obfuscated by then, the Microsoft acquisition had nothing to do with it.

If anything, looking back all the years, Microsoft has largely delivered on the promise to not fuck up the game and its community. They’ve mostly kept their hands off it, besides the Microsoft account stuff (which makes sense why they did it, but a lot of people are still understandably annoyed). Hell, they’ve kept up two separate codebases in fairly close feature parity for _years_. I doubt they’d have kept JE if there weren’t people in that team who genuinely cared.