Really enjoyed this episode of the local-first podcast with the Linear CTO: https://www.localfirst.fm/15. If you haven't looked up his talks on the Linear sync engine they're also fantastic.
I've really felt what he's saying about Linear's quality inspiring everyone to make software that's just as good, which really is impressive for an issue tracker!
And boy I'm really envious of the "built the frontend only" approach. There's a lot of momentum today swinging back to "just server-render HTML and don't bother with heavy JS frameworks". Which is all well and good... when you have a reliable internet connection. Local-first apps can run totally offline, but require a fully JS client.
I get what you’re saying about reliable internet connection. But I think the reality is most SPAs or JS framework heavy things these days necessarily are making API calls anyways.
I think it’s much rarer that you can keep all the logic on the frontend for long periods of time. That’s why just pushing your logic to the server side even for bad network connections seems more logical and simpler. At least from my point of view.
Of course it depends on the use case. I find it important to distinguish between the technologies themselves and how they're commonly used! There's no reason SPAs need to make network requests at all, but you're right that they usually are used to make apps which do.
As someone who feels a bit caught in both camps my hope is that as a community webdev can get to a "best tool for the job" mindset and have great options on both sides.
It feels like there's momentum building towards awesome new (in some cases more refined) tools no matter what approach is best for a given application and that makes me personally very excited
Last updated: Dec 12 2024 at 15:40 UTC