I introduced CCC to the world over 15 years ago. With the debut of CCC 5 within reach, I thought it would be neat to see how CCC has changed over the years. I still remember the day that I published a description on VersionTracker and anticipated the response. Would people like it? Would someone else beat me to the solution? I've been thrilled with the response I've gotten from users over the years, and I'm happy to say that I've grown this little seed into a successful company that produces and supports a great product.
Conception: November, 2001
Before CCC, I wrote an AppleScript that performed the very basic tasks of copying files from one volume to another while retaining Unix permissions and ownership. The Mac OS X bootable backup was born! This little script never saw the light of day, though. Instead, I made the extra push to turn it into an application that would be accessible to more people.
CCC 1.0: January 18, 2002
This was the quintessential "1.0" release. All of the basic features were there for a simple clone from the startup disk to a backup disk.
CCC 2.0: November 2002
2.0 allowed you to choose any volume as the source. Look at those fancy buttons! And a scheduler! Documentation!
CCC 3.0: September 2007
The long gap between 2.0 and 3.0 was not a break. I spent those years diving deeper into the startup procedure of Mac OS X and I learned a lot. I wrote other applications too, including one that was used to clone hundreds of Macs all at the same time. I was also having kids :-). I remember bouncing my son in his baby bouncer while writing code at 3AM for CCC 3.0. It's amazing that I can look at sections of code and remember those moments so clearly, like a smell can remind you of a childhood memory.
CCC 3.4: July 2011
There were several dozen releases of CCC between 3.0 and 3.4, but this was the first big one after I left Apple.
CCC 4.0: October 2014
Not long after Lion was introduced I completely stripped CCC down and rebuilt it. The result was spectacular – a refreshing new task-centric interface and scheduling that felt built-in, not added as an afterthought.
... Read More