judah

@joodaloop.com

906 Followers 173 Following

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.

a post on my website (https://joodaloop.com/riffs/joodaloop-v4.6/)
why is there no database built on changestreams that can be dynamically composed together for fan out? i.e. every write doesn't invalidate subscriptions (arbitrary, expensive to keep alive), but instead funnel into change-streams of sizes that are app-specific, like, per-repository, workspace, and user's notifications, etc. all combining into a single "user's stream"? i.e. logical subsets that don't change often instead of realtime queries or per-row versioning?
CLI output of `joodalint help`
CLI output of joodalint build checks
CLI output from joodalint
screenshot
better interface
roadmap for Pitter Patter libary
new version of sync engine architecture
Diagram describing the architecture of a sync engine