![]() ![]() Put another way, Apple thinks the last place you inter your data is on your device, they want to rent you a better version of yourself through their Colossus.įor this to work, device subsystems have to be very dependable, which is why the insides of Apple devices are soldered and glued together. To quote Sun-Ra "space is the place," or rather "RAM is the place." By closely integrating flash with RAM you can optimize the location of spatial-temporal layout of data to smooth the access to a dynamic cloud. So the question isn't how can the CPU help get data to the drive, but the other way around. That's where any data you immediately need to work on should be. Where does the data sent to the drive come to / go from but RAM. Think how you've identified drive DRAM as a being cache the Mac's CPU to flash, then identify system RAM as a cache for the cloud to the Mac device in the same manner.Įverything Apple wants is for your Mac to be a way-station for rented services it connects via the network.Įvery step of recent Apple device design has moved away from a PC-style unreliable bin-of-parts under the tyranny of the ruling OS to a more tightly integrated and reliable device package that provides an Apple customer a hookup to a tyranny of a ruling cloud service. ![]() Its not as tidy as a the concern overcommitting system RAM. Good questions with more implications for hacks. Building a CustoMac Hackintosh: Buyer's Guide ![]()
0 Comments
Leave a Reply. |