electric

Repping team Hyperfiddle here, we are super proud of: https://github.com/hyperfiddle/electric – a fully reactive Clojure dialect for web development that uses a compiler to infer the frontend/backend boundary. (BTW, Electric v3: Differential Electric is nearly here – Differential Dataflow for UI) https://github.com/leonoel/missionary – Supervised dataflow programming for Clojure/Script. For full-stack web developers who struggle to build correct and glitch-free applications, Missionary is a reactive programming toolkit based on process supervision, that lets you build massively concurrent, fine-grained reactive systems on both frontend and backend. Unlike promises and go-routines that make it easy to write a broken program, Missionary’s combinators provide the right set of constraints to let you build a fully composable program that is al

Opa was ahead of its time by at least 10 years. Have you seen Electric Clojure [0]? [0] https://github.com/hyperfiddle/electric

Electric Clojure backends already get such effect supervision for free (you'll need to manually tag sync/blocking effects). https://github.com/hyperfiddle/electric https://github.com/leonoel/missionary

As a self-taught seeker who spent 20 years in search of a better way, this is where I ended up for the heart of computer science. Most software engineering topics I picked up on the job — even distributed systems — but the actual computer science aspects I had almost zero exposure to at work. I had to seek those out, which meant rejecting the commercial methods/doctrines/thinking and escaping from Conway's Law which has infected anything touched by money. "It Is Difficult to Get a Man to Understand Something When His Salary Depends Upon His Not Understanding It" I now see actual CS exposure in industry as rare broadly (you'd have to work in a research org, which is both rare and also requires a PhD or other credential for one to be selected for the opportunity). Furthermore, the bulk of the CS literature & papers I encountered is embedded

As I understand it https://github.com/hyperfiddle/electric provides an abstraction at least over the network divide.

thanks ! https://github.com/hyperfiddle/electric live tutorial - https://electric.hyperfiddle.net/

UI is a high frequency concurrency problem. The “deep rooted usability problems” (like lag, glitches, and clumsiness - general lack of fluency) are due to staffing UI projects with web designers and not concurrency engineers. The fluent conversational AI systems and other movie UIs that folks are imagining up are therefore blocked on the concurrency sub-problem. This is the space we research at Hyperfiddle, we put forth our proposed solution here: https://github.com/hyperfiddle/electric

Electric Clojure - https://github.com/hyperfiddle/electric

You might find Electric in Haskell interesting: https://github.com/hyperfiddle/electric

https://github.com/hyperfiddle/electric ?

This should be present tense, at least in the ClojureScript case. Recent cool developments on that side include Electric Clojure - generating transparently state passing front and backend code from a single DSL: https://github.com/hyperfiddle/electric

how does Interaction Nets model compare with other concurrency models such as dataflow programming with Arrow? (For example, I maintain a distributed/reactive Clojure dialect for unified fullstack web development which seems to show a deep connection to HVM despite being based on dataflow not interaction nets - https://github.com/hyperfiddle/electric)