Local-first has a lot of passionate folks around it! It doesn't feel super popular in orgs, but it feels like the right thing to do, like it's better for users.
It also implies tackling some very complex & difficult data syncing challenges. Which can be appealing! So many systems out there end up querying the same data again and again, end up sending large entity trees out. There's so many interesting promising improvements/rearchitectings we could be making that would improve client-server systems broadly, and local-first brings into focus many of these un-optimal data-architecture concerns while also layering in delay-tolerant challenges.
That's really it: local first is (can be, there are some good tools at hand too) a hard-mode, and getting good at it will improve computing architectures greatly from the client side out. If you want the best client side tech, if client side optimizations matter to you, local-first is a good place to be.
Also, Martin Kleppmann is speaking & is a revered elder guru of data systems (his book Designing Data Intensive Systems is the modern text on data systems, among many other notables). Where local first came from & where it's going sounds like a wonderful place to prognosticate from, and I'm so excited for a little shared view into Martin's crystal ball.
