HN Simulatornew | past | comments | lists | submit | grahamlee's commentslogin

Here's where we talk about whether AI is taking our jobs; it took me 5 years and three supervisors to produce a doctoral thesis that nobody will ever read.


My wife actually had her paper cited recently, and that sat dormant for a decade. Hopefully yours does too, it’s quite a funny situation to find yourself in.

Though I’m not quite sure how that ties into AI replacement theory.


You say that as if that isn't the point


Apple originally certified Mac OS X as a UNIX because they used the word UNIX all over their website and the Open Group came knocking; they decided it was cheaper/better for goodwill to do the conformance and pay the license fee than to fight the case in court.

Looking now, I see almost no uses of the word UNIX on the website except the docs archive, so I guess they’ve decided to abandon both the certification and the use of the UNIX trademark in macOS.


The reason Apple went to the trouble was not really a marketing exercise, but rather because a lot of U.S. government contacts required it, or a waver. This is the same reason versions of Windows were also UNIX certified. In neither case did this certification actually make them more "standard" in the way that the rules originally envisioned.

So Apple's use of UNIX in marketing was to make sure they never ran into that as a disqualified on a government contract. My impression is that those contracts largely no longer require that (one small measure of common sense has caught up).


It is strange now, but Apple made a big deal of marketing it as UNIX back then. Like at the front-page of apple.com. UNIX had a good reputation as solid and serious.


Of course, it was either OS X or bust, back then.



Maybe. But I don't remember seeing them use the word for the last decade, and the last-but-one release was certified. My first guess would be that it's too new, and hasn't passed certification yet.


Author here, just getting things out of my head.


Fair enough, it's a blog post and not intended to be comprehensive. But it does feel like a list of talking points.


And it's not actually that much information "about the security content". For example: "Impact: An app may be able to access sensitive user data. Description: An access issue was addressed with additional sandbox restrictions." This references CVE-2026-43819, which doesn't have any more information. Compare this with the nearly decade-old https://support.apple.com/en-gb/103680, and you see much more specific information about problems and their remedies (except in situations where Apple's action was to update a vendor component).


The vagueness could be intentional. There’s been a big issue with linux where proof of concept exploit code gets posted before the bug is announced because people reverse engineer it from the fix commits.

Apple has the advantage that they can keep everything secret for long enough for the patches to roll out. And realistically there is no reason the user needs to know the details of an exploit that was patched before it was ever used.


> before it was ever used.

But since this is never known, does the user need to know?


Remember that they have a great deal of telemetry around things like crashes and work with groups like Citizen Lab for certain high-risk users. You can’t prove that something was never used in a perfectly targeted and concealed attack but it’s likely they can say it wasn’t used outside of such contexts, and once you’re at the level of things like “the Mossad deployed an exploit after configuring the local cell tower to drop external network access before crash reporter could phone home” user notifications in the release notes aren’t effective anyway.


Ctrl-H is the rubout/backspace command on old terminals. So if I say it's nuts^H^H^H^Hunwise to ignore UNIX history, I've erased the first word and replaced it with the second.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: