@Jonathan_Blow this is what I'd talk about if you ran a conference on simplicity. Why aren't game engines / level editors / photoshop collaborative? Because we have to rewrite that code every. damn. time.
Prikaži ovu nit
We're missing an API for data that changes over time. I think something like this could simplify dozens of existing systems. I can't count how many times I've implemented half baked versions of this sort of thing.https://josephg.com/blog/api-for-changes/ …
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Did you ever wind up giving https://github.com/amark/gun a try? It does most things you list. Even has a GraphQL extension that does GraphQL right. I disagree that remote peers should *have* to store change log. That is not as scalable and is the mistake most non-GUN CRDTs make.
-
I don't think remote peers need a change log either. Neither does the server in some designs. And not yet, but keen. I think gun is a bad fit for lots of the use cases I list in that blog post - like the list of active processes on linux. Many things have an authoritative source
- Još 4 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.