3 ms·
Well, it's always amusing how they discover that applications can run locally without depending on someone else's servers and maybe without pulling unverified c
by nottorp 2y ago
Well, it's always amusing how they discover that applications can run locally without depending on someone else's servers and maybe without pulling unverified code from 50 random repos.
Next they'll discover native applications! Innovation!
Maybe after that they'll even discover that you can give a shit about the user's battery/power consumption and ram consumption again!
- paulgb 2y agoThe key in local-first is the _first_. The stated goal is to give people the benefits of local applications (no spinners, data outlives the app) with the benefits of cloud applications (low-friction collaboration).
- kridsdale1 2y agohttps://developer.apple.com/icloud/cloudkit/ https://developer.apple.com/icloud/cloudkit/
- satvikpendem 2y agoThis is unnecessarily combative. Local-first does not mean local-only, it means that the app should also work on the internet, meaning that you need to solve sync, which is why it took some time for the concept to gain traction. CRDTs for example are relatively new.
- kridsdale1 2y agoI mean, native apps have been cloud syncing for more than 20 years.
- gessha 2y agoAs satisfying as it is to point at local first software and say they forgotten history, it’s important to remember that a lot of development happens where the friction is lowest. The target platform for many local first apps is browser because you don’t have to mess with EXE/DMG/AppImages. The goal is to ship, not to ship the most efficient application possible.