synch

To counter hardware issues, run several in synch in same way as old Tandem NonStop architecture.

Whiteout.io is a chrome app for email, plus an android app with key-synch between the two.

That's kind of a deal breaker – keeping in synch is (or should be) a higher priority than not skipping frames.

Let me assure you that bad synch algorithms have caused data loss before the cloud.

Services are easier to maintain backwards compatibility with, whereas databases are a massive pain to version and migrate and having to synch multiple teams to do such a job is a nightmare.

But for users it's better than the Excel spreadsheet that kept getting out of synch, or the painfully clunky google sheet or whatever.

First of all, we are keen to keep Typelevel Scala and the official Scala distribution in synch.

Although certainly there are a plethora of different kinds of IO bound problems (asynch vs synch or disk bound vs memory bound vs cache bound).

It's just a synch of data between peers.

So it's smooth but doesn't do synch properly?

Intelligent backups that only synch what you've changed.

Alas synching between different machines isn't easy (counter gets out of synch) and I'm not all that comfortable with keeping the databse in my owncloud.

While I do not agree with the premise of the quote, I don't find "customization" and "multi-device synch" tech-hipsterish - its exactly what happens with many phone app/webapp combinations.