![]() ![]() Apple started off being against "options" and complex dialogs, and more one way that the maker had decided was the best. Most of it is developer specific, but there's alot of technical overview stuff buried with it as well.įor terminal stuff, id muse that macos is carrying over a legacy from its "appliance" philosophy days. Specifically it makes the difference between "not possible" to some problems and maybe a fix. There's a few planets worth of content there, but its good to know about at least. If its not in one, it should be in another. That probably just confused you, but everything you could imagine is down one of those rabbit holes. The legacy apple developer guides are where all the details are for things like plists, services, demons etc, resource bundles (folders that appear as one file) etc. Its about as black box as linux is in that regard.Įverything else in the framework / middle comes from developer docs. ![]() Ie, if you jump into terminal and have a look, the same expectations will be met. Im not sure exactly how close osx is to bsd these days, but learning the structure of the os like you did for linux is also possible in mac. The nix stuff, there are features of the os that are only configurable via editing text config files etc. Ontop of this, consider keyboard shortcuts, applescript, automator, services etc. It doesn't take every long in macos to see every system preference there is and know what they do. ![]() Generally i've found there are 3 holes to dig down: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |