Those who are now beating up on the new 12VHPWR (although I don’t really like the part either) may generate nice traffic with it, but they simply haven’t recognized the actual problem with the supposedly fire-hazardous and melting connections or cables. Even if certain YouTube celebrities are of a different opinion because they seem to have found a willing object of hate in the 12VHPWR once again: This connection is actually quite safe, even if there are understandable concerns regarding the handling. However, the “safe” is only valid if e.g. the used supply lines from the power supply with “native” 12VHPWR connector have a good quality and 16AWG lines or at least the used 12VHPWR to 4x 6+2 pin adapter also offers what it promises. Which brings us directly to the real cause of the cases that occurred: It’s the adapter solution exclusively provided by NVIDIA to all board partners, which has fire-dangerous flaws in its inner construction! GPUs have gotten absolutely insane these last few years, and it was only a matter of time before something like this was going to happen.

Earlier this week, Apple released a document clarifying its terminology and policies around software upgrades and updates. Most of the information in the document isn’t new, but the company did provide one clarification about its update policy that it hadn’t made explicit before: Despite providing security updates for multiple versions of macOS and iOS at any given time, Apple says that only devices running the most recent major operating system versions should expect to be fully protected. I mean, this seems like typical for Apple, but the vagueness of it seems problematic. If I’m managing a large fleet of devices, I would definitely prefer the more detailed, structured, documented, and defined update and patching policies of professional Linux vendors or Microsoft.

It’s “release everything!” day for Apple – virtually every single Apple platform and operating system is getting updates today. Almost all device releases are point releases to address issues in the major versions released in September, with the exception being iPadOS 16, which was delayed and is accompanied today by macOS 13. Ars’ macOS review, is, of course, the definitive resource for this new macOS release. But it does feel like the software side of the Mac is lacking its own unique direction and identity lately. Overwhelmingly, new features for macOS merely help it keep pace with what is happening on the iPhone and iPad. That feels doubly true in Ventura, where a core system app has been rewritten from the ground up to mirror its iOS counterpart, where a new window management feature is being implemented in the same way on the iPad, and where new apps and updates to old ones are increasingly just iPad apps running inside macOS windows. The throughline for all these features is about making the Mac more welcoming and comfortable for people who come to it through one of Apple’s mobile platforms. This makes some sense. The Mac is Apple’s most powerful, extensible computing platform, both in hardware and software. It’s also the smallest. Maybe some of the first iPhone buyers were coming to it from the Mac, but the balance surely flipped years ago. But when was the last time that the Finder, the Dock, or the Menu Bar was given a substantial, non-cosmetic rethink? When did Apple last make major improvements to the way that windows coexist on a given screen? The Mac does get new under-the-hood features that are specific to it, but the headline features are mostly iOS and iPadOS imports, especially this year. You know where you can get the updates.

Tetris is a classic time-waster, both in and outside of the office. What good is any computing device if it can’t play this game? Tokyo System House certainly thought so, and ported it to the NEC mini5 line of CP/M-based word processors. Let’s preserve it for future generations and then see what it’s like! First, the author had to get their hands on a NEC mini5 word processor. Then, they had to somehow manage to find a copy of the game itself. Then, and only then, could the actual preservation attempt begin.

Error messages are part of our daily lives online. Every time a server is down or we don’t have internet, or we forget to add some info in a form, we get an error message. “Something went wrong” is the classic. But what went wrong? What happened? And, most importantly, how can I fix it? I really enjoyed this article detailing a massive project at Wix to go through and rephrase every single error message to make them easier to parse and overall less… Useless. A lot of developers can learn from this article.

To begin collaborating with others, we’ve open sourced several components for our secure operating system, called KataOS, on GitHub, as well as partnered with Antmicro on their Renode simulator and related frameworks. As the foundation for this new operating system, we chose seL4 as the microkernel because it puts security front and center; it is mathematically proven secure, with guaranteed confidentiality, integrity, and availability. Through the seL4 CAmkES framework, we’re also able to provide statically-defined and analyzable system components. KataOS provides a verifiably-secure platform that protects the user’s privacy because it is logically impossible for applications to breach the kernel’s hardware security protections and the system components are verifiably secure. KataOS is also implemented almost entirely in Rust, which provides a strong starting point for software security, since it eliminates entire classes of bugs, such as off-by-one errors and buffer overflows. Another new open source operating system by Google. This time, it seems almost entirely focused on embedded machine learning applications, so it’s definitely a bit outside of my wheel house.