There has been a lot of speculation/explanations offered over the years about why this functionality was removed from Disk Utility, but some of it is contradictory. I'd love to hear a definitive answer from the experts – what's the technical reason that Secure Erase is not offered for SSDs?

Is this functionality on the horizon or available in macOS 27? In lieu of snapshot reversioning, this would go a long way towards improving performance and logistics of restoring from a snapshot. For example, if I create a snapshot on a 2TB volume containing 1.5TB of data, then delete all of the files on that volume, it's logistically infeasible to restore that data back to the same volume without either snapshot reversioning or using clonefile() to recreate the file references on the live volume.

My app already has UI that allows the user to show/hide a menubar icon. If the user disallows my app's icon via System Settings > Menu Bar > Allow in the menu bar, I'd like to customize my own UI to reflect that. Does macOS provide a way for me to determine the "Allow in the menu bar" state for my application?

Referring to https://developer.apple.com/forums/thread/696431: The data protection keychain is only available in a user login context. You cannot use it, for example, from a launchd daemon. That's my scenario – I have a launchd privileged helper tool that needs access to keychain items (items that it creates and has exclusive access to, and items that may be required prior to user login). So this would appear to leave us with only one option – the System keychain. We can work with that (proof-of-concept shows that it works for us), but referencing the same forum post above: The file-based keychain is on the road to deprecation. So before I make a big migration to the System keychain, should I be concerned that the System keychain (being a file-based keychain) will go away in the future as well? If so, is there some other alternative that I should consider instead?