3 ms·
There’s way too many options on this site. It’s intimidating! How should I know which DB to use? I just wanna build stuff. For local-first to succeed as a conc
by ghiculescu 4y ago
There’s way too many options on this site. It’s intimidating! How should I know which DB to use? I just wanna build stuff.
For local-first to succeed as a concept, it would gain a lot from having a Rails equivalent that people can get started on. If that exists, promote just that and hide all the other options.
- clairity 4y agowhy doesn't rails have a local-first equivalent? it's something i'd love to see, as many apps can benefit. back in the day, we built a real-time sports stats app on top of rails and firebase (before it was gobbled up by google) that provided some affordances in that regard, but truly offline first--saving locally, then syncing when online--would be a great rails use case.
- yonz 4y agoI get your argument, cargo really gave Rust a leg up. Unfortunately we are far from having a go to platform. The community page's primary objective is to get the word out and connect local first builders.
- yunohn 4y agoThey said Rails, not Rust. Like Django for Python. I guess the answer is that JS/TS has never had a stack comparable to those py/rb behemoths.
- LAC-Tech 4y agoThere’s way too many options on this site. It’s intimidating! How should I know which DB to use? I just wanna build stuff. Multi-master systems - which you have if the same data is being written to by multiple devices - are complicated, and there's no one size fits all solution. The different approaches all have different trade offs. A good place to start might be "what do I think should happen when two bits of data that were updated independently are merged?".