What is Local first development
alexop.dev
What is Local first development
1–10 of 56 posts
Re: What is Local first development
#2> Effortless Collaboration: The app supports easy collaboration, even in offline scenarios.
mmm, yes, i see
Re: What is Local first development
#3Sync is still an unsolved problem. The solutions that claim to do it aren't very satisfactory.
Re: What is Local first development
#4Was hoping this to be about development happening on my host OS instead of containers/orchestrators.
Re: What is Local first development
#5> Picture using these apps offline with automatic synchronization when you’re back online. This is the essence of local-first web development – a revolutionary approach that puts users in control of their digital experience.
I had to laugh very hard at the "revolutionary approach". How is it revolutionary, if software was developed "local-first" for decades?
Techbros really do come up with the oldest ideas and call them revolutionary.
Re: What is Local first development
#6> Picture using these apps offline with automatic synchronization when you’re back online. This is the essence of local-first web development – a revolutionary approach that puts users in control of their digital experience. I had to laugh very hard at the "revolutionary approach". How is it revolutionary, if software was developed "local-first" for decades? Techbros really do come up with the oldest ideas and call t…
I laugh (maniacally) every time I need to change a jinja template generating a nightmarish yaml and remember the glory days of xml with affection.
Revolutions always have been the young one's business for a reason, I guess.
Re: What is Local first development
#7> Picture using these apps offline with automatic synchronization when you’re back online. This is the essence of local-first web development – a revolutionary approach that puts users in control of their digital experience. I had to laugh very hard at the "revolutionary approach". How is it revolutionary, if software was developed "local-first" for decades? Techbros really do come up with the oldest ideas and call t…
I suppose "local-first development" is a misnomer. It's really about the syncing part. Currently we have traditional applications that write data locally and therefore don't require an internet connection to work, and we have online stuff that updates a shared state "live". The "revolutionary" part would be having both of those things. It's a surprisingly hard thing to do.
The current state of the art here is git. So we're basically talking about making git automatic and easy to use for the majority of the population. That's not something we've been "doing for decades".
Re: What is Local first development
#8Was hoping this to be about development happening on my host OS instead of containers/orchestrators.
The phrasing threw me off too. I've usually heard of the OP's topic referred to as "local first software", not development.
Re: What is Local first development
#9Sync is still an unsolved problem. The solutions that claim to do it aren't very satisfactory.
Fully-generic character-level textual sync is an unsolved problem (and likely, always will be).
That's also not typically the best way to sync one's concrete data models, and if your data has any sort of structure, you can likely produce a merge operation that works Well Enough™ in practice
Re: What is Local first development
#10> Picture using these apps offline with automatic synchronization when you’re back online. This is the essence of local-first web development – a revolutionary approach that puts users in control of their digital experience. I had to laugh very hard at the "revolutionary approach". How is it revolutionary, if software was developed "local-first" for decades? Techbros really do come up with the oldest ideas and call t…
I suppose "local-first development" is a misnomer. It's really about the syncing part. Currently we have traditional applications that write data locally and therefore don't require an internet connection to work, and we have online stuff that updates a shared state "live". The "revolutionary" part would be having both of those things. It's a surprisingly hard thing to do. The current state of the art here is git. So…
I can think of so many pieces of software that does that: having a local state, having a remote state, and keeping them synchronized whenever internet is available. It's how email apps work. That's how all cloud drives work, and Dropbox is more than a decade old at this point. It's how notes apps work. Etc. etc.
Really can't see how this can be regarded as a recent idea.