Update 01/20/2011: Just when you thought it couldn’t get worse, Cultured Code tops themselves.
From ‘State of the Sync, Part II‘:
Neither Dropbox nor iDisk – or any similar service for that matter – were conceived as a sync solution for apps like Things.
This approach works to some extent, but it is slow and error prone to begin with, and advanced options like push or anything involving user-to-user data exchange is impossible.
These paragraphs would have more of an impact if I weren’t already using ~6 apps that sync between Mac & iOS using Dropbox / iDisk without any issues.
Then they get chesty:
In 2009 we switched our source code management system from Subversion to Git.
We were so intrigued that we decided to develop a sync solution based on Git’s core ideas
Hey, if you can’t pin the future of your company on an architecture that you yourself JUST started using then….wait, maybe don’t do that.
BTW, wouldn’t that have some large ramifications to Things itself?
This strategy required substantial portions of all versions of Things to be rewritten. It was clearly the most ambitious project we ever took on. Dissatisfied with our previous attempts, we didn’t want to settle with anything short of perfection.
We have tried many things, from underpowered technologies to over-engineered solutions. The approach we finally settled on is one that strikes the right balance, and in our next article we’ll be sharing more information about what that means.
I wished one of the solutions they tried was shipping something in the past 2+ years. But hey, with 3 weeks going by between Part I and Part II of this article, maybe they’ll be in a good position to hint at something by spring. I’m half expecting them to announce they’ve reconciled religion and science at this point.
Perfectionist and failure have more in common than people like to admit.