It’s a bit confusing to say “read these in chronological order” since it’s not immediately apparent that the document is ordered chronologically. It would be clearer just to say “read these in order”.
macOS Internals
11–20 of 146 posts
Re: macOS Internals
#12It’s a bit confusing to say “read these in chronological order” since it’s not immediately apparent that the document is ordered chronologically. It would be clearer just to say “read these in order”.
[dead]
Re: macOS Internals
#13Fascinating stuff, I've never really thought about what problem e.g. frameworks are solving. It's kind of too bad that in my day job my head's in the clouds and usually somewhat removed from most of these system level details.
inb4 it's just someone else's computer -- trust me I know
Re: macOS Internals
#14It’s funny how I used to think that operating systems, databases, and cloud systems, as these kind of arcane things that were somehow apart from the rest of software.
I could not begin to grasp how they could deal with running programs, access control, or any of these things that once seemed so foreign and mysterious to me.
And realising that it’s actually just software, that there’s no black magic to it, just lower-level APIs, less pre-built batteries-included stuff to rely on, and probably a whole lot of more complexity, that was… both mind blowing, exciting, and kind of a let down.
And it has enabled me to have more realistic expectations from these tools.
It however doesn’t take away any of the brilliance and effort that went into the these things, or lessen the credit due to those behind them. I can only begin to imagine the complexity involved in a full-fledged modern OS.
Re: macOS Internals
#15Fascinating stuff, I've never really thought about what problem e.g. frameworks are solving. It's kind of too bad that in my day job my head's in the clouds and usually somewhat removed from most of these system level details. inb4 it's just someone else's computer -- trust me I know
They’re just shared libraries.
Re: macOS Internals
#16Fascinating stuff, I've never really thought about what problem e.g. frameworks are solving. It's kind of too bad that in my day job my head's in the clouds and usually somewhat removed from most of these system level details. inb4 it's just someone else's computer -- trust me I know
They’re just shared libraries.
Thanks for the blinding insight.
Re: macOS Internals
#17It’s funny how I used to think that operating systems, databases, and cloud systems, as these kind of arcane things that were somehow apart from the rest of software. I could not begin to grasp how they could deal with running programs, access control, or any of these things that once seemed so foreign and mysterious to me. And realising that it’s actually just software, that there’s no black magic to it, just lower-…
It's turtles all the way down. Layers of abstraction stacked on layers of abstraction.
Re: macOS Internals
#18It’s a bit confusing to say “read these in chronological order” since it’s not immediately apparent that the document is ordered chronologically. It would be clearer just to say “read these in order”.
Thanks for the note; I may tweak that. Does the Highlights section's intro, "These chronologically-ordered highlights…" help?
—gist author
Re: macOS Internals
#19If you want to go even deeper there's the book series by Jonathan Levin
http://newosxbook.com/home.html for the lazy :) They are an updated and much expanded version of "Mac OS X and iOS Internals: To the Apple′s Core" by the same author. Which in turn was an updated version of "MAC OS X Internals: A Systems Approach" by Amit Singh.
Does anybody know why they are so hard to buy from outside the US?
Re: macOS Internals
#20Does anybody know how to force sandboxing for a 3rd party app?