artman

4 ms·

1.
by artman 3mo ago
https://github.com/jakearchibald/idb is a nice low-level wrapper for IndexDB that promisifies the API without much performance overhead.
2.
by artman 3mo ago
The HTTP request is fired off instantly, so chances are that the request is already written to the socket and closing the page won't cancel the request. Should your wifi-router drop it, your client will retain the transaction on disk a
3.
by artman 3mo ago
Operations are on average applied within a few hundred milliseconds, and almost never fail. Because of this we treat the success path as default, and indicate that your changes haven't been applied only if we detect that you're of
4.
by artman 3mo ago
In reality conflicts almost never happen.
5.
by artman 3mo ago
Changes go through and synced to everyone on your team in almost realtime. If there's a conflict on the server and your change cannot be applied (almost never happens), your change is rolled back on your client, again, almost in realti
6.
by artman 1y ago
For inspiration, you might want to look at what we open sourced at Uber, https://github.com/uber-archive/jetstream-ios and https://github.com/uber-archive/jetstream/wiki/Protocol . While
7.
by artman 1y ago
I think the impressive part here isn't Linear's sync engine, but the fact that Evan Hu went through painstakingly reverse-engineer the engine by inspecting traffic and obfuscated code and was able to write documentation that is co
8.
by artman 1y ago
Most certainly, if the data that the mobile app consumes is bounded and the same data is accessed frequently. Uber for example could have benefited from a sync architecture immensely (I tried to implement one back in the day, but was too la
9.
by artman 4y ago
We unfortunately don't currently have plans to provide self-hosting.
10.
by artman 8y ago
Very nice!
11.
Supercomputer passes turing test(engadget.com)
1 points by artman 12y ago|1 comments