HN user

john_alan

677 karma

A45F 8C27 C80F 5D4E 5CE0 EBD3 CA8E 83A6 4C18 5D8D RWRxmbgCt+0wPvdZ0alM7J46oqsOBTtud4E8zRznnCT0q0u7X971eWUN

Posts14
Comments286
View on HN

yep, dripping in AI.

It's a real problem, so many projects are adding features at breakneck speed, but with so many bugs and so little understanding.

Maybe that's just how it all works now, but I don't like it.

What you've said is emotionally compelling, but scientifically very weak. Personal recollection is selective and location-specific. You’ve described a memory, not established a mechanism.

What you perceive as change isn't macro, it's micro.

It doesn't mean macro change isn't happening, but it's not happening on our timescale.

I'm 50 FWIW.

I am repulsed by Tahoe's new design language.

I live in the vain hope that macOS 27 restores some sanity, at least maybe removes these clownish corner radiuses.

It makes the entire OS look like the Palm Pre's app switcher.

_A Mac with Apple silicon doesn’t permit native arm64 code to execute unless a valid signature is attached. This signature can be as simple as an ad hoc code signature (cf. codesign(1)) that doesn’t bear any actual identity from the secret half of an asymmetric key pair (it’s simply an unauthenticated measurement of the binary)._

_For binary compatibility, translated x86_64 code is permitted to execute through Rosetta with no signature information at all. No specific identity is conveyed to this code through the device-specific Secure Enclave signing procedure, and it executes with precisely the same limitations as native unsigned code executing on an Intel-based Mac._

Maybe it's Rosetta bins? - src from Apple:

https://support.apple.com/en-gb/guide/security/secebb113be1/...