@slightlylate clients depend on figuring out a generalized scalable backend.
-
-
-
@en_JS: um, no, users need a lack of data loss when conflicts occur. That's the hard UX problem here. See, e.g., CRDT & OT literature. - 1 more reply
New conversation -
-
-
What's really going to be spectacular is that these frameworks will likely graft *into* existing systems, not replace them. Colonization.
- 3 more replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@slightlylate agree about experimentation around data sync; however this is ultimately a server/distributed systems problem...Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@slightlylate you say this right when I discover the finer points of xdelta3/vcdiffThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@slightlylate and yes, a generalized solution will span server/client - this is about the next phase of app architecture. Not JS specific.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@slightlylate I mean this to emphasize rather than contradict your original statement: I agree data/sync will be explored in 2016.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.