3 ms·
What kind of work do you do? If it doesn’t involve writing Mac OS software, chances are you don’t need to know about that lower-level stuff. Even if it does, mo
by Someone 4y ago
What kind of work do you do? If it doesn’t involve writing Mac OS software, chances are you don’t need to know about that lower-level stuff. Even if it does, most programs nowadays use higher-level libraries than those working directly with the OS proper, so you might not need to know details there.
If you’re supposed to use the Mac as a tool, I would just start using it as a tool, and Google specific problems/issues if and when I ran into them. You seem to know the basics from your Linux experience, so chances are you’ll be fine that way.
I would think “advanced/expert Linux users” wouldn’t know about strace, the IP stack, etc. either.
- yaris 4y agoAt work I (usually) write networking software that is (or supposed to be) platform-agnostic. So for my main duty I don't need to know OS APIs and stuff. But I also often troubleshoot different issues when interaction (mainly through sockets) between our SW and customers' goes wrong. Here the named tools help quite a lot. Googling particular issues is natural, but I don't see it as the most efficient way to learn a tool.
- Someone 4y agoAha! That makes your question make sense. I haven’t used or even read it and don’t know whether it’s up to date, but you may want to start at https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/OSX_Technology_Overview/About/About.html https://developer.apple.com/library/archive/documentation/Ma..., and then, probably, click the “Kernel and Device Drivers Layer”. That, at least, should get you an idea about the terminology.