The past, present, and future of local-first - Martin Kleppmann (Local-First Conf)

Channel:Local-First Conf · Length:29:45 · Published:2024-06-18 · Views:17630

Watch on YouTube

Summary

Martin Kleppmann's Local-First Conf talk reviewing where the local-first idea came from, where it stands five years after the essay, and what the community should work toward. He argues for generic sync infrastructure.

Why HN recommends it

Cited in sync-engine and local-first threads for Kleppmann's argument for a generic, standardised sync protocol or service.

Martin Kleppmann in his talk last year spoke [1] the need for a generic sync protocol, which was very interesting. — HN, 2025

Software architecture & design · Databases & storage · Distributed systems

Subtitles (excerpt)

[Music] thank you so much Chad and it's I can't explain how how really excited I am to be here in such a large room full of people who are all interested in this idea of local first and all want to help make it happen so thank you so much for as Chad said being pioneers and being part of this movement I would like to talk a little bit about where local first came from at least from my very subjective perspective um do a bit of discussion about where I think we are today in terms of um understanding our the state of things and then where I hope we can all work to uh towards in the future over the coming years so starting with the history um my personal background and how I came to this topic starts uh over 10 years ago um so back in 2011 uh Mark Shapiro and his colleagues published this uh research paper on replicated data types or cdts which if you haven't heard about them don't worry uh it's kind of not really Central to the discussion here um but for me that was kind of the starting point because at the time I you know I was working in industry but I was a bit frustrated with the state of how we were building software for the web uh and you know software as a service and websites in general um and I was looking around for technologies

On Hacker News

There is a proliferation of sync tools and little standardization. Here some in local-first space [0]. Martin Kleppmann in his talk last year spoke [1] the need for a generic sync protocol, which was very interesting. [0] [LINK] [1] [VIDEO] — rapnie, 2025-05
> This is trying to solve a business problem (I can't trust cloud-providers) with a technical trade-off (avoid centralized architecture). I don't think that's quite correct. I think the authors fully acknowledge that the business case for local-first is not complexly solved and is a closely related problem. These issues need both a business and technical solution, and the paper proposes a set of … — samwillis, 2025-07
I see, I hear you. That isn't what local-first means, though. This is what local-first means: • [LINK] • [VIDEO] — sorrythanks, 2025-04
Martin Kleppmann in one of his recent talks about the future of local-first, mentions the need for a generic sync service for the 'local-first end-game' [0] as he calls it. Standardization is needed. Right now everyone and their mother is doing sync differently and building production platforms around their own protocols and mechanisms. [0] [VIDEO] — rapnie, 2025-03

Related videos