new blog post: https://x.com/dustingetz/status/1974442589764866260
A humbly pragmatic view of the revolutionary potential! When you put it like that it sounds almost gravitational. Clojures pragmatism (hosted, dynamism, etc) is the reason for its warts, but it’s also the secret weapon, allowing it to tread further despite odds. With all the new clojure langs fanning out across runtimes the value prop of a unified syntax gets more compelling. And electric is like a unified ui dsl. Instead of “write once run anywhere” as a set of compiled artifacts for different targets. It’s closer to “write once”, run in any runtime flavor, with a fully integrated ui layer that unifies client/server, and ultimately unifies the ui experience (for both dev and user) across runtimes.
e/client e/server has expanded into hostnames at this point, http://service1.acme.com, http://service2.bravo.com, http://ui3.acme.com
> e/client e/server has expanded into hostnames at this point, http://service1.acme.com, http://service2.bravo.com, http://ui3.acme.com > That's super interesting. So you're saying electric will be basically able to do rpc across arbitrary endpoints? And clj to clj as well?
yes but choreographies (efficient) not rpc (slow request waterfalls)
it's definitely a UI (i.e. application layer) focus, it's not necessarily clear that the backpressure model for example is identical in microservice<>microservice communication