Literally UNIX. www.opengroup.org/openbrand/register/
Comment on [deleted]
areyouevenreal@lemm.ee 2 months agomacOS isn’t Unix and doesn’t contain Unix code. It was based on FreeBSD which is “Unix-like” but has moved further and further away from that.
macOS also can’t just run all Linux applications. That’s nonsense. It doesn’t use the Linux kernel or its APIs and ABIs.
I am interested in what tools are missing on Linux that exist on macOS?
knemesis@sh.itjust.works 2 months ago
areyouevenreal@lemm.ee 2 months ago
Windows NT also used to be POSIX complaint. Is it Unix?
Maybe I care about things other than API and ABI compatibility, like I dunno actually having Unix code?
joneskind@lemmy.world 2 months ago
iOS development tools for starter.
A good enough WebKit browser for Technical acceptance testing
Ollama, LM Studio, for easy connection between Visual Studio and a local LLM
Visual Studio (The IDE, not the Editor)
Quality of life Apps
“Darwin is mostly POSIX-compatible, but has never, by itself, been certified as compatible with any version of POSIX. Starting with Leopard, macOS has been certified as compatible with the Single UNIX Specification version 3”
There are tons of ways to run Linux software on macOS maketecheasier.com/ways-run-linux-software-mac/
Now, can I talk to someone who actually knows what he’s talking about?
areyouevenreal@lemm.ee 2 months ago
Visual Studio on Mac isn’t the same as on Windows. I don’t know what you are using it for, but every time I have needed VS the mac version hasn’t been enough and I have had to use the Windows version.
Yes iOS and macOS development requires macOS. This isn’t really surprising. It’s like how Windows development requires Windows and Linux development requires Linux.
Actually containing Unix code and adhering to Unix APIs and ABIs (which is what the standard is) are two very different things. If meeting some API requirements is all you need that’s fine but you might as well call Linux and FreeBSD Unix too as they meet POSIX standards or close to it. Heck Windows was actually POSIX compliant at one point. Might as well call that Unix too.
As for that list article: Number 1,and 2 requires an application has been ported to macOS (you would know this if you actually read about and understand this stuff). An Numbers 3, 4, and 5 is just running Linux in a virtual machine and as a dual boot. I could run Windows or macOS applications on Linux using Wine and virtual machines, does that make Linux compatible with Windows and macOS? No.
6 is rebuilding a Linux project on mac which requires it to be source (and therefrom API) compatible.
Can I speak to someone who isn’t condescending to people with more accurate information than them?