Lightning talk! A Datomic Entity Browser for Prod — Clojure Conj 2025 #ElectricClojure

I developed something Datomic-like recently: github.com/maxweber/dbval

If you haven't checkout #electricClojure by @dustingetz you absolutely should. Great thread.

Datomic Cloud does not play well with @ElectricClojure. Only Pro works for my use-case. I’m tempted to build my own Datomic-like that only supports index access with different tuple semantics, because tuples are tricky.

And with the amazing @dustingetz we have a spectacular close to Day 1 of #LambdaConf2025 💪 You truly cannot miss Dustin's keynote on Electric Clojure: Differential Dataflow for UI ⚡ Check out the full talk in the link below! #ElectricClojure

m.youtube.com/watch?v=QIam96… @dustingetz 's keynote on $ElectricClojure is up. This is the way web UI should be built.

Two weeks until ReClojure in London! I’ll be talking about #ElectricClojure, join us! reclojure.org/

check out #ElectricClojure; a direct-style compiler for Clojure syntax to reactive signals based on functional effects, it uses a unified client/server AST to choreograph the frontend backend boundary at the expression level

I’ll be at the LambdaConf pre-conf hike, great time to hang out! And don’t miss the #ElectricClojure keynote on Monday!

"It’s truly a paradigm shift to be able to prototype/develop an app with the backend at the same speed that you would mock it in the frontend with a frontend db." Indeed! #ElectricClojure

Lighning talk! Electric Clojure in 5 minutes — Systems Distributed 2024 share.descript.com/view/nJkF… #ElectricClojure

@dustingetz's #ElectricClojure looks especially cool in this respect because it lets you put server and client code in the same function.

Oooohhh. Nice. I'm going to look at that. I'm on the same quest sort of. Settling on #electricclojure for building the backend and fronted. This could be a very good option to add to it.

better entity navigation ux coming soon to the datomic-browser demo - #ElectricClojure

Watch @36Rleonoel's talk on Missionary, the functional effects & streaming system powering @ElectricClojure: youtube.com/watch?v=xtTCdT6e…

One thing that sync engine advocates miss imo is that backends run in the edge now, and the edge is really close. Here from my home office, our prod app is literally 8ms away. When I virtual scroll over a 10k record collection, the timings are: FIRST PAGE LOAD: 8ms: send scroll offset to closest edge server 70ms: get from edge network to database in AWS (50ms for cross-continental, 100ms for cross-atlantic) 200ms: run database query once, return all 10k records to edge 0ms: retain result on session in edge 0ms: subvec over collection to read page 0ms: serialize one page of records 8ms: send one page of records to client 0ms: deserialize one page of records =286ms from user interaction to initial table load SUBSEQUENT SCROLL OFFSET CHANGE: 8ms: send scroll offset to edge 0ms: subvec over retained collection in memory 0ms: serialize one page of records 8ms: send one page of records to client 0ms: deserialize one page of records = 16ms from user scroll to next results That's 1 frame at 60 FPS! 60FPS virtual scroll over remote objects! This is why, with #ElectricClojure, we can stream results while hitting typical response latency of 20-30ms—gasp, horror, 1.5 animation frames—it is plenty! Those are pro gaming latency numbers! In video chat we consider this realtime! And Electric, being a reactive computation, auto-memoizes your edge computation for FREE! This performance for FREE!

Hey @dustingetz I have zero idea if this applies to #ElectricClojure, but it might.

See you at @lambda_conf! #ElectricClojure

Not even 30 minutes later, browsing the #ElectricClojure beta waitlist via convertkit API

Streaming HN client scrolling over stories and comments. Resolving content over HTTP to the CDN (visible rows only), as you scroll! #ElectricClojure