Local First has two primary hurdles to adoption in my mind:
1. Learning Local First currently starts at CRDT’s for most and this needs to be swapped with pure pragmatic “how do I do __ in Local First
1. Learning Local First currently starts at CRDT’s for most and this needs to be swapped with pure pragmatic “how do I do __ in Local First
Comments
All a workplace will hear is “we need to change our architecture completely”
Would you be interested in setting up a call and talking further?
Could be a great workshop as well
I feel the company I work for might be at a great point for this type of thing but we are using planetscale/mysql so its been a bit more difficult to find a good solution for that
Would love to use Electric!
The alternative is frustration cause it feels like people would rather “do it the hard way” when mostly people just don’t know what they don’t know
No need to start from scratch.
Now Local First is a bit different, is not UI but actual data, so no idea how to achieve that
I do think @kyle.bricolage.io and the Electric team as well as the team working on ZeroSync have great setups for incremental adoption
Progressive enhancement is a bit different ->
Progressive enhancement means Im starting server first where Local First means client first, at least it tends too so that you don't have to rely on servers
You start with server rendered data and then replace with client data. There are more elegant patterns and implementations but it is possible just not the norm
This is mysql using planetscale, is that what would be supported in the future?