I eagerly anticipate that getting posted. FWIW, the obstacle I perceived for trying to do disconnected operation is that you can't tell if a
On Wed, Jul 16, 2014 at 6:55 PM, Joseph Gentle <jose...@gmail.com> wrote: > Yes, as far as I know its impossible (Or at least impractical - you'd > need to have garbage collection). But thats ok - implementing a rich > text type is *easier* than implementing a JSON type. > I didn't know rich text was easier than JSON, although I suppose it sorta makes sense from outside. I forsee garbage collection or similar housekeeping processes to be difficult to reconcile with disconnected operation (such as is likely for mobile users) without sometimes informing the disconnected user that their operations cannot be accepted. > > I recently paired with the author of quilljs and stypi to port his > rich text OT type for quill into sharejs. It works great. > I eagerly await publication of that. For one thing, rich text seems to be the major missing piece before ShareJS can be the core of a Wave replacement (Etherpad, on the other hand, appears to lack the ability to store anything *but* rich text). > > My big learning from a lot of this stuff is that semantics for > different kinds of data are different, and you need to be able to > support that in your system. > > -J > Amen to that. JSON gets you *most* of the way, as in lots of things can be made to fit. I figure Wave would have run into the same thing if it had gotten widespread enough for people to try to represent things other than Wavey conversations (for instance, atomic replacement of attributes is suboptimal for SVG).
