3 ms·
At 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 a
by yaris 4y ago
At 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.