Elaborations on this approach:
- https://news.ycombinator.com/item?id=34948816
- https://github.com/papers-we-love/papers-we-love/blob/main/d...
1,169 karma · joined August 20, 2012
Elaborations on this approach:
- https://news.ycombinator.com/item?id=34948816
- https://github.com/papers-we-love/papers-we-love/blob/main/d...
What I can get running in a weekend for my personal use would:
- take 20 days (10x) to turn into something that other teams in the same company can easily consume without much effort on their part
- take 200 days to turn into a public facing product that people would actually use instead of their current thing
IMO, this is why engineers so often look at products and think "Oh, I can build that in a weekend"
I've created plenty of toy languages and reactive UI libraries in a weekend. People may find inspiration and take some ideas from my 2 days of work but nobody is going to use those as a replacement for their current thing without the next 198 days of effort.
A small example: if you can create a "spreadsheet to website generator" in a few hours, it'll be a month before you've built it out enough to launch a product around it that will attract users.
If you're open to resolving those I'd love to stick it into cr-sqlite :)
You can also pick up the mount vernon trail in Roslyn along with the Custis trail if you bike.
They’re trying to make it more of a spot and do weekly free concerts in the park there these days.
tldr -- this matches my experiences as well.
For a simple case of two nodes, they'll be divergent until each node sends the other their current state.
For client-server, the "whole system" wouldn't be in the same state until all clients report all their changes to the server and the server re-broadcasts all those changes to all clients.
A pathological case (but happens when people leave an ipad in a drawer or something) -- a node could be offline for 6 months and the rest of the system never gets those changes until that node comes back online. There's technically some divergence: the other nodes are missing whatever state the ipad had, but does it really matter if that node was unimportant enough to be left offline?
Depends on use case for sure.
D1, unfortunately, doesn't support loading extensions into SQLite.
fly.io, and their sqlite solution, does however!
I've been using fly.io to run cr-sqlite in the cloud and act as a sync server for non peer to peer use cases. Eventually I'll have finished up a re-write of strut.io[1] atop vlcn/cr-sqlite which'll serve as a good end to end example of how to make applications with this sort of architecture.
Some discussion about this setup on the fly.io forums: https://community.fly.io/t/litefs-many-tens-to-hundreds-of-t...
I'll try to get to that.
Other GC research unrelated to this project but something I've been following: https://braid.org/antimatter
Given the use of SharedArrayBuffers and that SharedArrayBuffers can't be used in a shared worker (funny), SQLite WASM doesn't work in shared workers.
If getSyncAccessHandle was made synchronous then maybe everything would just work. It'd also improve SQLite WASM perf by 30% according to their measurements [1]
[1] https://sqlite.org/forum/forumpost/af64f73911e5410cf9a640c9e...
Example of syncing your app across tabs with SQLite here: https://vlcn.io/docs/guide-solving-tabs
Projects like https://readyset.io/, https://materialize.com/, https://github.com/mit-pdos/noria can keep your materialized views up to date as the underlying base tables change.