mrpippy

For some reason, the PS4 and PS5 actually cannot play audio CDs

These links show the pinout:

https://hardware.majix.org/computers/sgi/keyboards.shtml https://hardware.majix.org/computers/sgi.pi/keyboard.shtml

And the keyboard(7) man page actually has full details on the protocol (Indigo uses the mini DIN-6): https://github.com/jtsiomb/sgikbd/blob/master/doc/sgi_man7_k...

Also, SGI keyboards never used ADB. Indigo-era SGIs used a mini-DIN keyboard/mouse, but it was proprietary. They were PS/2 starting with the Indigo2 and Indy.

My memory from classic Mac OS is that pushing the keyboard soft-power key brought up a system-modal dialog asking if you wanted to shut down, restart, or cancel, a dialog with exactly the same design as: <http://www.christianboyce.com/page25/files/tipofthedayjulyth...>

That would obviously not be compatible with a server, maybe if soft power was just constantly held down starting from boot that dialog wouldn't show up?

The author discussed this a bit on Mastodon as well:

https://xoxo.zone/@numist/116716469017975106

At this point that would be a 2018 Mac mini, which can only run Sequoia (which will be out-of-support at the same time as Homebrew drops Intel support).

If you want Intel support, MacPorts still runs back to Leopard.

Virtualization.framework just gained USB passthrough support in macOS 27. It might be a niche feature for containers to add, but other VM software will likely add support soon.

I would consider HFS+ to be a legacy filesystem at this point, something you shouldn't use without a really good reason (interop with pre-macOS 10.13 machines being the only one I can think of).

Fun fact: HFS dates back to the 80s, and so does the fsck code. https://github.com/apple-oss-distributions/hfs/blob/main/lib... still contains '#if BSD' blocks for the Mac OS X code, and classic Mac code in the '#else'.

And 'dfalib' refers to 'Disk First Aid', the classic Mac fsck application.

Note to the author: did you file an Apple feedback for this? You should put that FB number in your post and the GitHub repo, it will ease the process for any Apple employees who see this and want to get it fixed.

Right, that’s why you get a simpler yes/no dialog for notifications, and a conplex “navigate to this settings pane and click a separate button” flow for a keylogger

Those are still needed for the Rosetta use-cases that are sticking around (old games, Linux binaries)

I feel like that's true for early/mid-90s games where the PC version targeted DOS (+ the varied universe of PC video/sound hardware), and the Mac version could just target the much more uniform Mac platform.

But SimCity 3000 is from 1999, and the PC version was a normal Win9x game. I own (still have the CD) the SimCity 3000 Mac port, and it is not very good. Maxis didn't port it themselves, it was done by Software MacKiev. System requirements were quite high for the time, it was sluggish, often unstable, and the file open/save dialogs reused the Windows-style dialogs which was very awkward.

The soundtrack is great though.

WinCE 6 Platform Builder was based on Visual Studio 2005 I think.

Building applications for WinCE 6 was also only supported with Visual Studio 2005 or 2008, which put a hard cap on available language features and development OS support. I had the thankless job of trying to port C++ code from Linux to WinCE 6 in 2014, and even then VS2008 felt way behind.

See https://developer.apple.com/documentation/macos-release-note...

Correct, that is staying around.

https://developer.apple.com/documentation/macos-release-note...:

There will continue to be support for older, unmaintained gaming titles leveraging Rosetta along with software running Intel binaries in Linux VMs.

True, Apple's developer and support pages are not all fully up-to-date or explicit. From the macOS 26.4 release notes (https://developer.apple.com/documentation/macos-release-note...):

There will continue to be support for older, unmaintained gaming titles leveraging Rosetta along with software running Intel binaries in Linux VMs.

No, those need to stay (at least the ones needed to run the targeted "old unmaintained games"). What can go is all the x86_64 slices of system binaries (i.e. bash, perl, etc etc)

Evidence that NVIDIA has even been trying? My understanding is that Apple didn’t allow 3rd parties to write graphics drivers past 10.13, but they could’ve done a non-graphics driver like this.

I believe it was the first RISC that Apple prototyped building a Mac around, including a 68K emulator. IIRC from Gary Davidian’s CHM oral history, it was corporate dealmaking that led to AIM and PPC more than any technical negatives for the 88K.

https://computerhistory.org/blog/transplanting-the-macs-cent...

The report says it broke when updating from macOS 15 to 26, so not a minor patch update. I'm a bit surprised no one noticed this earlier though, since 26 has been out since September and in beta since June.

AppleScript doesn’t have any NeXT heritage, it comes entirely from classic MacOS (debuted in System 7.1)

This leak has been floating around for years, and it's not even close to everything (i.e. no GUI pieces)

Apple is shipping code built with this, and is supporting it for developers to use (see https://developer.apple.com/documentation/xcode/enabling-enh...)

Huh? They're all linked from https://support.apple.com/en-us/102662

CarPlay supports that, the car just needs to pass it through. I believe Ford and Toyota both do.

The original article is here, and it unfortunately is just as confusing: https://www.reuters.com/business/intel-ceo-says-company-will...

Of course Intel has been designing and selling GPUs for years, I guess Lip-Bu means they're going to start manufacturing them as well? Or they're going to be data-center focused now?

Are you talking about Starliner? Starliner's 2 flights have been problematic to say the least, but Orion's single (uncrewed) flight went pretty well.

Various anticheat/DRM schemes actually do direct syscalls on Windows, so Proton has patches that use seccomp to trap them and jump to the intended Nt* syscall. There was actually a feature added to the Linux kernel a few years ago (syscall user dispatch) so that Wine could stop using seccomp for this, but Wine is still not using it.

Upstream Wine also supports direct syscalls on x86_64 macOS. macOS syscall numbers have a high bit set, so Windows syscall numbers (0 to ~300) are invalid macOS syscalls, that triggers SIGSYS, and then Wine jumps to the Nt* syscall.

How are they explaining away the fact that the Japanese male astronaut asked for a consult with the flight surgeon on the public loop (a video which NASA has since removed from YouTube)?

Everyone on the ISS needs to have a seat reserved for them in a docked spacecraft, in case they need to evacuate the station quickly (or for a medical issue like this). You can’t bring back just one person from a 4-person crew; the other 3 would have no way to leave.