|
|
|
|
|
|
by mantas
1485 days ago
|
|
|
Okay, then maybe that local-first sync can easily support multiple schemes and let old versions run without overhead to devs? Personally I'm fed up with syncing both as a user and as a developer. As a developer, I don't want to deal with infrastructure for an app. It's a massive headache to have 24/7/365 responsive system. I want to make apps, not be on-call sysadmin. As a user, I don't want to worry who is going to sell my data after going bankrupt. And I'd prefer small dev shops don't waste their time on keeping network infrastructure up and running with security patches. |
|
|
I'd love that. Ink & Switch has done extensive research on how to enable this with p2p technology etc. Our industry isn't there yet... but lots of good folks are working on it. The Muse sync setup is a step in that direction.
> As a developer, I don't want to deal with infrastructure for an app. It's a massive headache to have 24/7/365 responsive system. I want to make apps, not be on-call sysadmin.
Oh yes. I spent many years carrying a pager for Heroku's infrastructure. Part of the appeal of local-first is the sync infrastructure is necessary to transmit data between devices, not for every single keystroke or gesture the user makes.