5 ms·
Yes - but even then... it's not really true unless your site is completely static resources. If you're pushing a blog out - Great! If you're pushing out anyth
by horsawlarway 4y ago
Yes - but even then... it's not really true unless your site is completely static resources.
If you're pushing a blog out - Great!
If you're pushing out anything that relies on application state... much less great.
At best, you then end up in a world of trouble dealing with eventually consistent data, sharding/tenanting, CRDTs, "edge" KV stores (that are really just hiding the eventually consistent nature from you) and all sorts of other trade offs.
If I'm directly collaborating with some half way around the globe in a web application - there is literally no magic way to wave a wand and make that latency go away.
- Existenceblinks 4y agoOne thing I don't understand CRDT hype is it doesn't solve semantics conflict problem, and solving it on app level would also be better by-passing CRDT completely. And one more thing, real-time collaboration just mean road without sign, lines, traffic light. Having process in place, in async way, is considerably more efficient.
- davidatbu 4y agoI'm currently looking into using CRDTs for a side project, and would love to pick your brain: CRDTs don't solve the semantic issue of a conflict, but nothing ever will, because the semantics are defined by business requirements, right? Isn't the idea behind CRDTs to develop a set of "primitives" upon which one can build conflict free data structures? And isn't all the hype about CRDTs a result of the fact that providing those primitives in a serverless way (ie, without requiring a central authority) was a hitherto unsolved problem?