And how game developers solved the web's biggest problem in the 90s

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

Developers of a to-do app, 'ChoreCommander,' struggle with modern web app issues like offline functionality and real-time collaboration. The team debates various tech stacks before Ethan suggests using a sync engine, akin to those used in 90s game development, to solve these concerns. Sync engines manage network interactions and maintain local state, allowing for offline reads, optimistic updates, and real-time collaboration. This architecture promises improved responsiveness and simplicity for complex web apps.

Why is everybody talking about sync engines?

<p>you’re the first person i’ve heard talking about sync engines.</p>


<p>If you’re in the browser world we call this IndexDB with lots of sync-to-server tools and options.
In you’re not in a browser we simply call this a local DB.
But this article does not address the biggest challenge of syncing which is order of precedence. in the article they only stick with a simple use case of adding the new value to the existing value - which completely ignores the difficult use cases.</p>
