Electric Clojure v3: Differential Dataflow for UI [video]

Post by diggan » Thu, Aug 22, 2024, 4:42 PM UTC

lispisok wrote: post #30

TheMagicHorsey wrote: post #24

As much as I love lisps, and I've written a fair bit of code in Scheme, Racket, and Clojure, I have to admit, when you are an immigrant in another person or organization's code, their specific abstractions, DSLs (macros), etc., can be very (VERY) burdensome to get up to speed on to even begin to start contributing to the codebase (much less debugging complicated issues). On the other hand, there is a ridiculous amoun…

Your comments about Go make sense since it was no secret Go was designed to get junior engineers at Google up to speed being productive as fast as possible.

Post by dustingetz » Thu, Aug 22, 2024, 5:08 PM UTC

teoingdri wrote: post #25

Love Clojure, but am repulsed by the idea of a “responsive DOM network stream”. This feels over engineered to me. The classic cool factor influencing the “if we could vs if we should”, bolstered by developing it as a software engineer on a performant dev box with impeccable internet connection; hell, maybe even a local dev db clone. I suppose you could argue server side caching would alleviate some of the pains of a…

    (defn window [xs offset limit]
      (subvec (vec xs) ; fast cast
        (Math/max offset 0)
        (Math/min (+ offset limit) (count xs))))

    (e/defn Window [query! offset limit]
      (e/server
        (let [xs ($ e/Offload #(query!))] ; retain and reuse xs as offset changes
          [(count xs) (e/diff-by identity (window xs offset limit))])))

Post by diggan » Thu, Aug 22, 2024, 5:17 PM UTC

mgdev wrote: post #34

I hate stuff like this. It's so incredibly brilliant that it spoils me for mainstream tech, but it's never actually "done enough" for mgmt to feel comfortable adopting it in any capacity. (See also: Unison https://www.unison-lang.org/ ) Or, you can get them to adopt, but then you hit hiring limitations. I say this as someone who built a large team of Clojure developers in a Fortune 100 company, and lived to regret it…

Post by isker » Thu, Aug 22, 2024, 5:28 PM UTC

dustingetz wrote: post #17

amw-zero wrote: post #3

What I’ve never understood about this approach is that it claims to be “network transparent,” but you need to add client and server annotations. So it’s very much network-aware.

The site macros (e/client & e/server) let the programmer declare what site an effect must run on. The network is not explicit, only implied. For example, platform calls like (query-database) or (.createTextNode js/document) or (check-password) are inherently sited. Siting is essential complexity (arguably the essence of a distributed system), and consequently we as programmers are hyper-aware of where (at which site)…

Post by barrell » Thu, Aug 22, 2024, 5:51 PM UTC

sabbaticaldev wrote: post #16

BaculumMeumEst wrote: post #2

I've found that the gap between generative AI's ability to generate code for mainstream languages and niche languages such as Clojure is growing. It is getting much better at generating code for the former, and continuing to flounder for the latter. How do Clojure folks feel about that? Do you disagree, or maybe see it as a non-issue?

when AI can code clojure it’ll be called “AGI”