Linear sent me down a local-first rabbit hole (bytemash.net)

Article summary

The article discusses the author's exploration of local-first web development after using Linear, a project management tool that feels impossibly fast. The author delves into the technical details of local-first development, including the use of IndexedDB and sync engines. They also explore various tools and libraries, such as Jazz, Electric SQL, and Zero, that aim to make local-first development easier. The author concludes that local-first development can provide a better user experience, but it also comes with trade-offs and challenges.

Main themes

• local-first development
• web performance
• frontend frameworks
• backend infrastructure
• mobile vs web
• productivity and collaboration
• database design
• sync engines
• JavaFX and DOM diffs
• client-server architecture trade-offs

What commenters say

• Some commenters argue that local-first development is more suitable for mobile apps, where internet connectivity is not always guaranteed, rather than web apps.
• Others believe that the web is the primary platform for productivity and collaboration, and therefore local-first development is more relevant for web apps.
• There is a debate about the role of frontend frameworks in slowing down web applications, with some arguing that they are the main culprit and others blaming inefficient architectures and databases.
• Some commenters think that globally distributed databases and complicated backend infrastructure are not necessary for achieving low latency, and that a well-designed frontend and efficient event processing system can achieve similar results.
• The use of JavaFX to stream DOM diffs to the browser is seen as an example of a fast and modern website, but others point out that it may not be suitable for mobile devices.
• There is a discussion about the trade-offs between using local-first development and traditional client-server architecture, with some arguing that the benefits of local-first development outweigh the costs.
• Some commenters argue that the industry is moving in the wrong direction by prioritizing frontend complexity over backend performance.
• Others believe that the web enables experiences that were previously impossible, and that modern web tech is not the primary cause of slowdowns.