Or do the same basic troubleshooting you would for any other computer. It sounds like the person you're replying to doesn't know how to do that. They should learn. It's not that hard.

[+] [email protected] -8 points 2 weeks ago (1 children)

Debugging a Mac is just as simple as debugging a Linux OS… because it is Linux.

[–] [email protected] 14 points 2 weeks ago (2 children)

I can't tell if you're making a joke or just confidentially incorrect

[–] [email protected] 7 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Well, macOS is unix based, and when debbuging a friends mac, I usually find that I find the terminal more comfortable than the Windows Command Prompt.

Now, that Mac does break in very weird ways sometimes, but I digress.

[–] [email protected] 6 points 2 weeks ago (1 children)

Linux Is Not UniX

[–] [email protected] 5 points 2 weeks ago

Also Gnu is Not Unix

[–] [email protected] 3 points 2 weeks ago (1 children)

It’s a lot simpler to say Linux to keep the conversation going than it is to say Mac is BSD based and therefore is a Unix system and has all the exact same benefits of a Unix based system. There is no joke here, maybe you just like correcting people when they’re trying to have a conversation.

[–] [email protected] 3 points 2 weeks ago

Calling something Linux is very specific, and it's just not true for macOS. E g. if someone brings you an encrypted drive that uses LUKS, you can't mount it in macOS. But both are Unix-like, macOS even being UNIX certified. However, from what I understand, these mostly concern a specific part of the stack that doesn't guarantee that you can work with the other system, this is rather something for applications to target. I mean cool I can enter a shell and list files on macOS, but that doesn't fix the problem.