this post was submitted on 12 Apr 2024
940 points (94.0% liked)
Technology
59577 readers
2939 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
macOS 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?
Literally UNIX. https://www.opengroup.org/openbrand/register/
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?
https://en.wikipedia.org/wiki/Darwin_(operating_system)
"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 https://www.maketecheasier.com/ways-run-linux-software-mac/
Now, can I talk to someone who actually knows what he's talking about?
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?