judah
@joodaloop.com
visit joodaloop.com for my stuff
stick around for tweets about scatterpad.com, my magnum opus. i also made streams.place a couple years ago.
stick around for tweets about scatterpad.com, my magnum opus. i also made streams.place a couple years ago.
Pinned
new riff on my site, where i talk about how i have a fondness for the simplicity of *non-realtime* sync
joodaloop.com/riffs/collab...
joodaloop.com/riffs/collab...
February 10, 2026 at 10:54 AM
new riff on my site, where i talk about how i have a fondness for the simplicity of *non-realtime* sync
joodaloop.com/riffs/collab...
joodaloop.com/riffs/collab...
lmao i should have mentioned it's realtime collaborative
rowsy.intpub.workers.dev
minimal spreadsheet editor (made mostly by @ampcode.bsky.social) with me directing and choosing the tech stack:
- @solidjs.com
- @automerge.org
- partykit.dev
works without logging in, new spreadsheet at each URL, very similar to what @tldraw.com does for it's pages
minimal spreadsheet editor (made mostly by @ampcode.bsky.social) with me directing and choosing the tech stack:
- @solidjs.com
- @automerge.org
- partykit.dev
works without logging in, new spreadsheet at each URL, very similar to what @tldraw.com does for it's pages
February 9, 2026 at 11:12 PM
lmao i should have mentioned it's realtime collaborative
rowsy.intpub.workers.dev
minimal spreadsheet editor (made mostly by @ampcode.bsky.social) with me directing and choosing the tech stack:
- @solidjs.com
- @automerge.org
- partykit.dev
works without logging in, new spreadsheet at each URL, very similar to what @tldraw.com does for it's pages
minimal spreadsheet editor (made mostly by @ampcode.bsky.social) with me directing and choosing the tech stack:
- @solidjs.com
- @automerge.org
- partykit.dev
works without logging in, new spreadsheet at each URL, very similar to what @tldraw.com does for it's pages
February 9, 2026 at 11:00 PM
rowsy.intpub.workers.dev
minimal spreadsheet editor (made mostly by @ampcode.bsky.social) with me directing and choosing the tech stack:
- @solidjs.com
- @automerge.org
- partykit.dev
works without logging in, new spreadsheet at each URL, very similar to what @tldraw.com does for it's pages
minimal spreadsheet editor (made mostly by @ampcode.bsky.social) with me directing and choosing the tech stack:
- @solidjs.com
- @automerge.org
- partykit.dev
works without logging in, new spreadsheet at each URL, very similar to what @tldraw.com does for it's pages
Reposted by judah
this is how design works
February 9, 2026 at 5:34 PM
this is how design works
"the creative fields demand great patience "
- me, logging out of twitter again
- me, logging out of twitter again
February 9, 2026 at 6:40 PM
"the creative fields demand great patience "
- me, logging out of twitter again
- me, logging out of twitter again
has anybody built something spreadsheet-like with @automerge.org? i don't need formulas and stuff just an editable grid really
February 8, 2026 at 2:51 PM
has anybody built something spreadsheet-like with @automerge.org? i don't need formulas and stuff just an editable grid really
i hope @solidjs.com 2.0 switching to async rendering doesn’t mean things like triggering animations or other imperative code gets harder…really looking forward to writing more things in Solid soon
i have faith in @ryansolid.bsky.social though, the time slicing stuff is great
i have faith in @ryansolid.bsky.social though, the time slicing stuff is great
February 7, 2026 at 10:41 PM
i hope @solidjs.com 2.0 switching to async rendering doesn’t mean things like triggering animations or other imperative code gets harder…really looking forward to writing more things in Solid soon
i have faith in @ryansolid.bsky.social though, the time slicing stuff is great
i have faith in @ryansolid.bsky.social though, the time slicing stuff is great
i am not going to call it a sync engine, it's more of a simple sync architecture
it will not slot into existing backends like all the other sync engines are trying to, it will force a very particular way of writing server code
but it will be a good way
it will not slot into existing backends like all the other sync engines are trying to, it will force a very particular way of writing server code
but it will be a good way
- sync partitions
- snapshot materialisation
- subscription sets
are all it should need
- snapshot materialisation
- subscription sets
are all it should need
February 7, 2026 at 3:04 PM
i am not going to call it a sync engine, it's more of a simple sync architecture
it will not slot into existing backends like all the other sync engines are trying to, it will force a very particular way of writing server code
but it will be a good way
it will not slot into existing backends like all the other sync engines are trying to, it will force a very particular way of writing server code
but it will be a good way
still need to figure out the two parts of the client-side database:
- the IndexedDB layer (probably borrow the KV-store implementation from the replicache.dev codebase)
- the in-memory query layer (would be nice to have some kind of IVM layer, based of d2ts)
- the IndexedDB layer (probably borrow the KV-store implementation from the replicache.dev codebase)
- the in-memory query layer (would be nice to have some kind of IVM layer, based of d2ts)
February 4, 2026 at 5:44 PM
still need to figure out the two parts of the client-side database:
- the IndexedDB layer (probably borrow the KV-store implementation from the replicache.dev codebase)
- the in-memory query layer (would be nice to have some kind of IVM layer, based of d2ts)
- the IndexedDB layer (probably borrow the KV-store implementation from the replicache.dev codebase)
- the in-memory query layer (would be nice to have some kind of IVM layer, based of d2ts)
i’m sure workers.dev is amazing to have as an infrastructure primitive, buts it’s never made a lot of sense for app-like usage of your edge server has to talk to a distant database anyway
but with async local-first it’s the perfect low-cost fit, simply shuffling data along slowly
but with async local-first it’s the perfect low-cost fit, simply shuffling data along slowly
workers.dev
February 4, 2026 at 8:57 AM
i’m sure workers.dev is amazing to have as an infrastructure primitive, buts it’s never made a lot of sense for app-like usage of your edge server has to talk to a distant database anyway
but with async local-first it’s the perfect low-cost fit, simply shuffling data along slowly
but with async local-first it’s the perfect low-cost fit, simply shuffling data along slowly
one part of local-first i still don't buy is the interoperability story
everyone i know is very passionate about it but i almost never want to open one app's data in another one
and when i do, exporting to a standardised format is what i really care about
everyone i know is very passionate about it but i almost never want to open one app's data in another one
and when i do, exporting to a standardised format is what i really care about
February 3, 2026 at 9:38 PM
one part of local-first i still don't buy is the interoperability story
everyone i know is very passionate about it but i almost never want to open one app's data in another one
and when i do, exporting to a standardised format is what i really care about
everyone i know is very passionate about it but i almost never want to open one app's data in another one
and when i do, exporting to a standardised format is what i really care about
what percentage of popular dev tools actually use modern hardware "correctly"?
February 3, 2026 at 7:32 PM
what percentage of popular dev tools actually use modern hardware "correctly"?
thinking about “compute slices”
February 3, 2026 at 6:53 AM
thinking about “compute slices”
new productivity system...
→ make multiple todo lists in scatterpad.com
→ every morning, pick tasks from across them to do that day
→ do them
→ make multiple todo lists in scatterpad.com
→ every morning, pick tasks from across them to do that day
→ do them
February 2, 2026 at 10:44 PM
new productivity system...
→ make multiple todo lists in scatterpad.com
→ every morning, pick tasks from across them to do that day
→ do them
→ make multiple todo lists in scatterpad.com
→ every morning, pick tasks from across them to do that day
→ do them
joodasync v2.0 design so far:
write path through event log, all mutations are semantic, idempotent and affect a single item
read path through database objects, using the event log as a way to only send back objects that have changed
write path through event log, all mutations are semantic, idempotent and affect a single item
read path through database objects, using the event log as a way to only send back objects that have changed
February 2, 2026 at 6:18 PM
joodasync v2.0 design so far:
write path through event log, all mutations are semantic, idempotent and affect a single item
read path through database objects, using the event log as a way to only send back objects that have changed
write path through event log, all mutations are semantic, idempotent and affect a single item
read path through database objects, using the event log as a way to only send back objects that have changed
metaframework for CRDTs should also include some kind of UI library
February 2, 2026 at 8:41 AM
metaframework for CRDTs should also include some kind of UI library
how do we feel about eventual consistency? defensive app code’s not too fun is it?
February 1, 2026 at 12:51 AM
how do we feel about eventual consistency? defensive app code’s not too fun is it?
Reposted by judah
That’s uncertaintyslop. You only like it because you’re epistemically humble
January 31, 2026 at 4:00 PM
That’s uncertaintyslop. You only like it because you’re epistemically humble
constraints enjoyers how we doing today?
February 1, 2026 at 12:35 AM
constraints enjoyers how we doing today?
s2.dev seems really cool, might deserve a sync engine or two to be built around it
S2, the durable stream API
The serverless API for unlimited, durable, real-time streams
s2.dev
January 30, 2026 at 8:45 PM
s2.dev seems really cool, might deserve a sync engine or two to be built around it
logged out of twitter to focus on my personal website
January 30, 2026 at 8:10 AM
logged out of twitter to focus on my personal website
hex.kitlangton.com is quite nice, makes me wish i was good at transcribing instead of thinking through typing
HEX
VOICE → TEXT
hex.kitlangton.com
January 30, 2026 at 8:07 AM
hex.kitlangton.com is quite nice, makes me wish i was good at transcribing instead of thinking through typing
i am going to make the world’s most unimpressive sync engine
January 27, 2026 at 6:33 PM
i am going to make the world’s most unimpressive sync engine