Discussion: The Primary Limiting Factor of Offline-First #45
Description
IMHO one of the strength of web-apps is that you can choose whatever backend you run. You are not locked in to JS/Node.
Now I don't know if it has been addressed, but going offline-first the biggest hurdles are actually running the app-servers on the client. Running PHP, Ruby, Python, Elixir, Java, Rust, Clojure, Scala, Go, Perl, Lisp, Scheme, Haskell etc. app-servers on the client. And: Running web servers on the client fitting into those ecosystems.
So imho the starting point is making available slimmed down toolkits for the most famous of those server side technologies. Then, and only then, offlinefirst will mature into distributed/decentralized/auto-synching apps.
Requesting offlinefirst seems to request from you to pay the price of double-apps (instead of distributed/decentralized/autosyncing apps) tech-locked into javascript/v8 (maybe ELM is to the rescue).
Where am I wrong - because I am, most likely?