Cool Blob Future Mac OS
adminMay 31 2021
Cool Blob Future Mac OS
The font uses native OS light font but has a fallback for older OS’s that don’t support truetype fonts. The 'True Type' font will be applicable for most modern OS’s. In the case of the 'native:' fonts Android devices will use Roboto whereas iOS devices will use Helvetica Neue. Most modern machines do, but if you are unsure you can find out more here for Mac OS X. Some additional notes about different models: Kinect 1414: This is the original kinect and works with the library documented on this page in the Processing 3.0 beta series. On Mac, all the apps that I’d want to open are in the /Applications directory and for the most part all have a.app extension, so we can get their names using something like this: d = '/Applications' apps = list(map(lambda x: x.split('.app')0, os.listdir(d))) List the directory and remove the extension. The film sequel, TRON: Legacy, is actually an interesting subversion — when you consider that the OS that everyone uses was made by a hacker, it makes sense that all the computer use a Command Line Interface, making for something of a Linux future. The control room for the Arena in The Hunger Games adaptation has an Apple-like aesthetic. This video shows you how to download blob videos and convert them to other formats like MP4, MKV, MOV, etc. On Mac using Cisdem Video Converter: https://bit.
Monday, 10 April 2006
When I wrote about Boot Camp Thursday, I started by observingthat while I and many others were initially shocked by Apple’sannouncement, it only took a few hours before the idea seemedcompletely obvious and not really surprising at all.
Boot Camp has opened the door for a lot of additional speculationregarding what this means going forward for Apple. I think it’s onlyfair for me to go on the record regarding which of these ideasreally would be shocking, if they were to come to pass.
Regarding anything related to Apple’s strategy going forward, it’sessential to keep in mind just how Apple functions as a business.It’s not very complicated. Apple now has two fundamental businesses:selling Macintosh computers and selling iPods. And I think if youwanted to, you could argue that this is really one core business,selling computers, and that some of their computers are Macs andsome are iPods.
I’m not offering this as anything other than a statement of theobvious, but it’s apparently not so obvious to many of the punditsspeculating on Apple’s future plans.
Selling hardware is their business. That’s where their revenue comesfrom, that’s where their profits come from, and revenue and profitis what defines a business. Everything else they do is in support ofthis core business. Apple is famous for its software — both the MacOS and their own Mac applications — but they make way less moneyselling Mac software than they do selling Mac hardware. And theiTunes Music Store is just the equivalent of “software” for iPods.
And so that’s the prism through which one needs to view Applespeculation. For any idea, ask yourself this: Would it help Applesell more Macs or more iPods? If the answer is “no”, Apple isn’tgoing to do it, or, if they do, it’d be a genuinely shockingdevelopment.
I forget to do this myself occasionally. On Thursday, I wrote:
All Apple needs to do to be spectacularly successful with itscomputer business in the next few years is to take just a fewsingle digits of market share away from Windows.
But that doesn’t actually quite make sense, because “Windows” — orthe company behind it, Microsoft — doesn’t actually sell PChardware. If Apple is going to grow a few extra percentage points ofcomputer hardware unit sales, those points must come at the expenseof PC makers.
If this growth is driven by Boot Camp (and/or Parallels Workstation,or VMware for Mac, or an Intel-native version Virtual PC, or anyother means of running Windows on Mac hardware), Microsoft may noteven “lose” anything at all, because customers driven to the Mac forthis reason must also buy Windows if they want to run it.
Boot Camp doesn’t pit Mac OS X against Windows, and so it doesn’tpit Apple directly against Microsoft. What Boot Camp does is pit Machardware that can run both Mac OS X and Windows up against allother PC-hardware that can only run Windows.1
Apple Is Going After the Profits, Not the Mass Market
If Apple takes a few additional market share points, it will be atthe expense of companies like Dell, Toshiba, Lenovo, and Sony.What’s essential to note is that they’re not just going after anyand all of the PC market — they’re going after the high end, whichis to say, the profitable end.
Nicholas Carr agrees with me, and he nails it in his analysis of whyBoot Camp matters:
As I’ve said many times before (too many, in fact), the consumerPC market has, like other consumer markets before it, split intotwo basic segments: buyers of commodities, and buyers of premiumgoods. The money’s in serving the latter. That’s why, forinstance, Dell just bought Alienware.
In reference to my line that “Instead of choosing between a WindowsPC or a Mac … you now get to choose between a computer that canonly run Windows or a computer that can run both Windows and Mac OSX,” Carr continues:
I think that’s the reason the Apple’s stock price has shot upnearly 20% since the Boot Camp announcement yesterday. It’s notthat Apple may be able to expand its general market share by acouple of percentage points; it’s that those percentage points arelikely to represent many of the most attractive customers in themarket.
And that’s Apple’s strategy in a nut.
What would be interesting would be to see computer manufacturers’“market share” computed in terms of profits, rather than unit sales.Apple almost certainly makes more profit from a $600 Mac Mini soldthrough one of its own stores or Apple.com than eMachines does froma $500 POS PC sold at Wal-Mart. But in terms of “marketshare”, they each count as one computer sold.
Whatever Apple’s “profit share” of the PC industry, it must be muchlarger than its 2-5 percent market share. And Apple’s strategy seemsclearly geared toward ramping up profits, not just unit sales.
Why Apple Isn’t Going to Release Mac OS X for Other PCs or License the Mac to Other PC Makers
One contrary view to Apple’s Boot Camp announcement, espoused bothby Paul Boutin in Slate Friday and Robert X. Cringely in anop-ed Saturday in The New York Times, along with numerousother pundits and webloggers high on Boot Camp fumes, is that BootCamp isn’t bold or important at all, and that what Apple reallyought to do is release a version of Mac OS X for generic PChardware. As Boutin puts it:
Cool Blob Future Mac Os Catalina
Instead of a disk that allows you to boot Windows on a Mac, whatabout a disk that lets you boot OS X on any Intel-powered PC? Idon’t want Windows on a Mac. I want OS X on a PC.
Cool Blob Future Mac Os 7
The reason this isn’t going to happen — at least not soon — isthat it doesn’t fit with Apple’s aforementioned business, sellingcomputer hardware. Boot Camp fits because it makes it more likelythat more people will buy Mac hardware, and doesn’t make it any morelikely that existing Mac users will switch to buying computers fromsome other company.
Cringely writes:
This strategy would turn Boot Camp on its head, as the companyselling all those $140 [sic] retail copies of its operatingsystem would be Apple. And with hundreds of millions of Windowsmachines in the world, getting even 1 percent of PC users toswitch to OS X would be a huge new business for Apple. It wouldalso create another headache for Microsoft. And that, in theend, is what Apple does best.
The problems with this logic are manifold. For one thing, gainingone percent of the market by selling one percent more of the totalcomputers would be way more profitable than selling that many $130copies of Mac OS X.
According to Apple’s quarterly financial statements, thecompany in recent years has consistently hit gross profit margins atad over 25 percent. Apple does not (publicly) break these marginsdown on a product-by-product basis, but I think 20-25 percent is areasonable estimate of their profit for most of their big-ticketproducts.
So, let’s say today Apple makes $500 in profit on a $2,500 MacBookPro. Tomorrow, in Boutin’s and Cringely hypothetical world whereApple sells $130 copies of Mac OS X for any PC, they might makeabout $100 in profit when someone buys a Sony Vaio and a copy of MacOS X.
Cringely’s statement that “getting even 1 percent of PC users toswitch to OS X would be a huge new business for Apple” ignores thefact that it might also completely sabotage Apple’s existing andvery profitable business of selling Macintosh computers. Cringelyseems to be making the assumption that everyone who’s currentlyusing Apple hardware would keep buying Apple hardware, and thatthese retail copies of Mac OS X that run on generic PCs would besold only to new customers.
If that were the case, sure, it would only add to Apple’s success.But that wouldn’t be the case. There can be no doubt that manycurrent Mac users would buy other-branded hardware, costing Applehundreds of dollars in profits. To make up for each such loss, Applewould need to gain three, four, or maybe even five new customers.
That’s not to say all Mac users would abandon Apple hardware. Buthundreds of thousands would, and Apple would need to gain millions ofnew switchers just to compensate for that lost revenue and breakeven; otherwise they’d lose money on the endeavor, even whilegaining many more users of Mac OS X.
Boutin clearly recognizes that this would in fact happen:
Face it, most of your time at the computer is spent interactingwith the operating system and applications, not admiring the case.OS X is an excellent operating system, with a lovely, soothinginterface that doesn’t wriggle like a bug. Why not run it on thecheapest computer you can get? If you cracked open a new Mac andtook stock, you’d realize you could buy the same computer muchcheaper by ignoring its packaging. Once you got rolling on e-mailand Web surfing, you might even forget what your PC looks like.What matters is what’s onscreen.
Leave aside for this discussion the fact that you can’t actuallyget a comparably-equipped computer from any other company forthat much less than Apple’s current Intel-based Mac line-up —you can get much cheaper computers, sure, but not much cheapercomputers with comparable components. The point here is thatBoutin is right that what matters most is what’s on-screen.
Unlike Cringely, Boutin even acknowledges that Apple tried somethinglike this a decade ago:
Sound crazy? Apple actually tried this, allowing othermanufacturers to produce “Mac clones” for two years during SteveJobs’ absence from the company. “The styling of the Mac clonesoften more closely resembled that of a PC,” Wikipedia notesaccurately, “but the clones frequently offered a lower price andsometimes better performance.” Bill Gates himself proposed theidea in an earnest 1985 letter to then-Apple CEO JohnSculley shortly after Jobs’ ouster. Sculley passed on the idea,leaving a successor to try it, perhaps in desperation, 10 yearslater. Jobs killed the clone program when he retook the helm in1997. He’s since locked Apple’s software into onedifferent-thinking hardware product after another, from theoriginal iMac to the iPod nano.
But Boutin’s claim makes it sound like Jobs killed the Mac cloningprogram out of spite. Wrong. Jobs killed the cloning program becauseit was killing Apple Computer financially. Recall that during theMac clone era, most of the mainstream press coverage of Applecentered around speculation that the company was on the verge ofcollapsing into bankruptcy. Apple did not profit from the cloningprogram, for the same reasons outlined above: many Mac usersswitched from buying Apple hardware to clone hardware, and Applemade much less money from Mac OS licenses than it did from sellingMac hardware, and there was nowhere near enough growth in the userbase to make up the difference.
It’s just not true that most Mac users use Macs because the hardwareis better designed. They’re Mac users because of the Mac OS. Whatthe original cloning program showed was that many of Apple’scustomers were Mac fans, not Apple fans.
Now it’s true that Apple’s current industrial design is far betterthan that of typical cut-rate PC makers, and aesthetically it’s evenfurther ahead today than it was a decade ago, when Apple itself wasstill making “beige boxes”, albeit nice beige boxes. But it’s notthat much better than other high-end PCs. Sony Vaios and LenovoThinkPads, for example, are fine laptops. And it’s on high-endmachines like good laptops and powerful PowerMacs — the machinesApple makes the most profit on — where Apple would be most likelyto lose sales. They can’t say, “Here’s a license for Mac OS X butyou can only install it on low-end machines”, and nor can they sellMac OS X licenses for the $400 or $500 profit margins they make onhigh-end hardware.
The ’90s Mac cloning program was popular with many Mac users becausethey were able to purchase faster computers for less money.
I’m not going to say it’s impossible that Apple could be successfulwith such a plan, but I do think it’s unlikely. And unquestionablyit would require completely changing the company’s business model,abandoning the current model that has proven to be consistentlyprofitable for a commodity model of making much less money pertransaction and making it up on volume. Anyone who denies that sucha plan would be risky either doesn’t understand Apple’s currentbusiness model — which is, as repeated ad nauseum herein, sellingcomputer hardware at 20-25 percent profit margins — or is makingthe completely unrealistic assumption that all current Mac userswould continue buying Apple-branded hardware. Remember too thatApple’s current business model is bootleg-proof; unlike Mac OS Xinstaller DVDs, you can’t burn copies of MacBooks or iPods.
Why Would Apple Want to Compete Directly Against Microsoft?
Cringely signs off his op-ed with this claim:
[Licensing Mac OS X for generic PCs] would also createanother headache for Microsoft. And that, in the end, is whatApple does best.
Really? Creating headaches for Microsoft is what Apple does best?When has Apple ever created headaches for Microsoft? And beforeyou say “iPod and ITMS”, note that that’s a new market that Appleconquered first, not a market where Microsoft had already gained afoothold. If anything, it’s the other way around: historicallyMicrosoft has created far more headaches for Apple than vice versa.
Microsoft’s biggest headache is the long-delayed Vista, and that’s aself-inflicted wound.
I think what’s happening is that guys like Cringely and Boutin, whoare tasked with writing about the computer industry at large, havegotten bored with Microsoft. They still need to write aboutMicrosoft because it remains the biggest, most influential, andmost profitable company in the industry, but Microsoft has nothreatening rivals. Vista (née Longhorn) is turning out to be one ofthe biggest debacles in industry history — they’re sheddingfeatures and it still keeps slipping further behind schedule.Imagine how far behind schedule they’d be if they were stillplanning to include all of Longhorn’s originally slated features.
And yet the Vista debacle isn’t really hurting Microsoft at all,other than in the technology press. They’re still making money handover fist each quarter.
Would it be exciting if Steve Jobs were to stand up at his nextkeynote address and say, “We’ve decided to license Mac OS X to anycomputer maker that wants it, and our goal is to put Microsoft outbusiness”? Most definitely. But it’d be exciting in the way thatit’s always exciting to watch someone else do something reckless andrisky.
It’s not Apple’s fault that Microsoft sucks to write about, nor isit their obligation to put themselves on a collision course againstMicrosoft just because it would make for good drama, and thus,something interesting to write about on the tech beat.
Cocoa for Windows
One more thing-Apple-won’t-do: release a version of Cocoa forWindows. Back in the ’90s, after Next stopped making its owncomputer hardware and turned into a software-only company, theydeveloped a version of the OpenStep application framework that ranunder Windows (and other OS’s). Shortly after the Apple-Nextacquisition-cum-merger, Apple released a preliminary operatingsystems roadmap in which the application framework we now know asCocoa was called “Yellow Box”.
The real Mac OS X doesn’t bear much resemblance to these preliminaryplans, which (the initial plans) really amounted to little more thana revision of NextStep with a classic Mac OS compatibility layer,which layer was called “Blue Box”. There were no plans for what wenow know as the Carbon APIs — i.e. in these initial plans, there’dhave been Classic for old-style Mac applications, but there’d havebeen no way to write native applications other than Cocoa.
Another part of this initial plan was to maintain the cross-platformYellow Box libraries, the idea being that developers could write(what we now know as) Cocoa applications and have them run both onMac OS X and on Windows. This wasn’t a pipe dream, Next actually hadthis working in the OpenStep era.
Much to the consternation of some developers, this plan was soonscrapped as well.
Rumors of its resurrection persist, and while I haven’t seenany high-profile punditry positing its imminent return, I’vereceived a bunch of emails from readers wondering if Boot Campsomehow means Yellow Box for Windows is coming back.
Viewed through the aforementioned “keep in mind at all times thatApple’s core business is selling computer hardware” filter, theanswer is clearly no. A Cocoa runtime library for Windows might wellmake developers happy, but it wouldn’t help sell Macintosh hardware.
Quite to the contrary, it’d take away one the main reasons peoplebuy Macs: to run cool Mac applications. If the whole point of theappeal of Mac OS X is that Mac software is better than Windowssoftware — or at least better in the eyes of one segment of themarket — what possible good would it do Apple to help thatsoftware run on Windows, too?
The continued existence and success of Mac OS X hinges on thepremise that it is better than Windows. If all or most of the appspeople love on Mac OS X ran just as well (or nearly so) on Windows,it would lessen the degree to which Mac OS X offers a betterexperience. Cocoa for Windows might well prove wildly popular forsome Cocoa developers, but it wouldn’t make money for Apple andcould potentially cost them in hardware sales, so it isn’t goingto happen.
Please don’t argue that Apple would gain hardware sales becausemany Windows developers would switch to Cocoa and buy Apple hardwareon which to develop their software. Even if we assume it’s true thatApple would gain new developers (which is admittedly a reasonablyfair assumption), and that those developers would buy Applehardware,3 there just aren’t thatmany developers out there compared to the number of civilian users.It’d be foolish to gain a few new developer customers if it meantlosing many times more regular users who decided thatWindows-with-Cocoa was good enough for them.
“Oh, but then Apple could sell iLife and iWork to Windows users”isn’t a good argument either, because, repeat after me, Apple’sprimary business is selling computer hardware.
Cool Blob Future Mac Os Download
And the best way for Apple to sell more computer hardware is to makeMac OS X as much better than Windows as they possibly can; nothingcould be further from this goal than releasing a version of Cocoafor Windows.
Feel free to substitute “Windows and other PC operating systems such as the various Linux-based distributions” for “Windows” if you’d prefer. ↩︎
Personally, I always thought the Mac clones were pieces of junk, at least the ones from PowerComputing and Umax, and most people I know who bought them regretted it. You got what you paid for, more or less. ↩︎
Note that this argument — that Apple would profit from Cocoa-for-Windows by selling hardware to former Windows-only developers — presupposes that Apple isn’t going to do the “license Mac OS X for generic x86 hardware” thing. ↩︎
| Previous: | Windows: The New Classic |
| Next: | Seriously, ‘Repair Permissions’ Is Voodoo |
CCC 5.1.23+ can make bootable backups of Big Sur on Intel-based Macs.
Update Nov 24:CCC 5.1.23 can now make bootable backups of a Big Sur startup disk on Intel-based Macs. Support for System volume cloning on Apple Silicon Macs is disabled for now because Apple's APFS replication utility does not currently work on that platform. When Apple fixes that, we'll post an update to CCC that restores support for making bootable backups on Apple Silicon Macs.
CCC is a native application on Apple Silicon and is 100% compatible with Apple Silicon Macs
CCC will automatically proceed with a Data Volume backup when backing up an APFS Volume Group on Apple Silicon Macs — that's a complete backup of your data, applications, and system settings. If you would like to make your Apple Silicon Mac backup bootable, you can install Big Sur onto the CCC Data Volume backup. Please keep in mind, however, that your CCC backup does not have to be bootable for you to be able to restore data from it.
With the announcement of macOS Big Sur, Apple has retired Mac OS X (10) and replaced it with macOS 11. As with every upgrade since the original release of Mac OS X, we have to make changes to CCC to accommodate the changes in this new OS. As the numeric change would suggest, though, this is the biggest change to macOS since Apple introduced Mac OS X roughly 20 years ago. The system now resides on a 'Signed System Volume'. This volume is cryptographically sealed, and that seal can only be applied by Apple; ordinary copies of the System volume are non-bootable without Apple's seal. To create a functional copy of the macOS 11 System volume, we have to use an Apple tool to copy the system, or install macOS onto the backup.
Does this mean that we can no longer have bootable backups?
I can certainly understand why people are concerned about the future of this solution. Thanks to these massive system changes and some bugs in the version of Big Sur that Apple intends to ship, nobody can make a proper copy of the System volume right now, not even with Apple's proprietary utilities. Based on that statement alone, and a suggestion from one of my competitors to just give up and use Time Machine instead (which does not make bootable backups, nor back up the System), someone could falsely conclude that it's impossible to have a bootable backup.
I think that pessimistic conclusions are also fostered by a concern that Apple is trying to turn macOS into iOS, or otherwise merge the two platforms. On top of that we're in the midst of a pandemic, and one would hope that Apple would cool their jets and defer these massive changes for a year. But no, we're not just getting a massive new OS this year, we're getting a new hardware platform too! We're seeing a lot of change at a time where we could really use some stability.
The changes in Big Sur definitely present some new logistical challenges, butyes, you can have a bootable backup of macOS Big Sur. Right now you can install Big Sur onto your CCC backup to make it bootable, and in the future we'll use Apple's APFS replication utility (ASR) to clone the Big Sur System volume. Apple has assured us that they are working towards fixing the problems in ASR that prevent it from cloning the Big Sur System volume.
Does my CCC backup have to be bootable for me to restore data from it?
No. Bootability is a convenience that allows you to continue working if your startup disk fails, but it is not required for restoring data from a CCC backup. You can restore individual folders and older versions of files (i.e. from snapshots) using CCC while booted from your production startup disk. CCC backups are also compatible with Migration Assistant, so you can use Migration Assistant to restore all of your data to a clean installation of macOS (e.g. on a replacement disk).
Here's why I'm really stoked about this new, 'proprietary' macOS, and optimistic about the future of bootable backups
Every year we spend hundreds of hours making changes to CCC to accommodate the new OS. Every year. CCC isn't like other apps that can easily roll with the changes; our solution is tied so closely to the logistics of the startup process, and that happens to be something that Apple has been changing a lot since the introduction of APFS. The logic changes required to accommodate APFS volume groups alone are mind blowing. All of that time spent is subtracted from the time we can spend on feature work. To put it plainly, we spend about a quarter to half of our year just making CCC work with the next year's OS. That's not a shiny new feature that users can swoon about (and pay for!), it's typically thankless work, and – fair or not – work that users have come to expect us to provide for free.
What if we didn't have to take the responsibility of making the startup logistics work on the backup disk? What if Apple provided that part of the solution? What if all we had to do was make the best backup of your data, apps and system settings, and then let Apple handle the logistics of the System? We'd be dreaming, right?
In fact, Apple has been making key parts of the startup process proprietary for years, but they've also been developing functionality within macOS that handles the proprietary parts. All the way back to the beginning of Mac OS X, in fact, we'll start with the 'bless' utility, which makes changes to the volume headers to make a volume bootable. We've been using bless for 20 years! Over that time bless has been adapted to the changing OS and hardware landscape, because Apple uses it too. With the introduction of APFS, we've had to leverage more Apple utilities; primarily diskutil, a command-line version of Disk Utility. We really started leaning on diskutil in Catalina for the manipulation of APFS volume groups. Finally, in macOS 10.15.5 we got the 'opportunity' to field test another Apple utility that has lurked in macOS since Mac OS 9: Apple Software Restore (ASR). ASR is a utility that Apple has used in factories to 'stamp' the system image onto every Mac, and more than a decade ago I developed a mass deployment solution around that utility. Like with the bless utility, Apple has been adapting ASR for APFS, and Apple is going to make ASR work with Big Sur too.
In the near future, I expect to be able to leverage ASR within CCC (again) to clone the Big Sur System volume, and then use our own file copier for maintaining backups of the data that actually matters – your data, applications, and system settings. That would create the perfect division of responsibility: Apple is responsible for the copying of its proprietary OS, and CCC is responsible for the backup of your data. All of this, though, will be neatly wrapped in the Carbon Copy Cloner bootable backup solution.
We need to share our concerns productively with Apple
It's easy to complain about how things don't work the way they used to (go ahead and get me started on Big Sur's new alert dialogs and progress indicators!). Rather than complaining, or giving up, though, we need to make it clear to Apple that we want these solutions, and we need to make it clear when they don't work. We can do that with bug reports, and to that end, we've been very transparent about our bug reports to Apple on issues within macOS that affect CCC, e.g.:
But we can also send a clear message to Apple with our choices. If Apple ships macOS Big Sur without fixing the underlying utilities that facilitate creating a bootable backup, you can choose to defer the upgrade. There is no urgency, no impetus to upgrade to macOS Big Sur. If we defer the upgrade choice, that sends a clear message that we're willing to wait for Apple to deliver quality software, rather than hitting an artificial deadline with an OS that's not ready.
In the meantime, if you're an early adopter by choice or by profession, you can still make your CCC backups bootable. CCC will automatically handle the logistics of making a complete backup of all of your data, applications and system settings. Once you have that, simply install Big Sur onto your backup to make it bootable. Again, we're planning to automate that part of the procedure in the future, but we've tested this scenario extensively and we're prepared to support it.
CCC 5.1.22 is qualified for use on macOS Big Sur, and this update is free for all current CCC v5 license holders. We have some additional resources that folks should check out as well as they consider the Big Sur upgrade:
Cool Blob Future Mac OS