sorry_i_lisp

> drk points out that the SSE stream is one-way but your app isn't

oops

Clojure on JVM with virtual-threads (green threads) and communicating only via core.async channels (CSP inspired) using immutable data structures is pretty neat, FWIW.

Thank you! I also use it.

Finally someone is speaking truth to power. These registered non-profits that release their code for free and their leisure time for support need to be knocked down a notch.

We all know they are evil. But you know the most evil thing? That code that was previously released under a free license? Still sneakily on display in the git history like the crown jewels in the Tower of London. Except of armed guard defending the code that wants to be free once more it's hidden behind arcane git commands. Name me a single person that knows how to navigate the git history. I'm waiting. Spoiler alert: I asked Claude and they don't exist.

No value judgment, what do you mean by "JVM madness"?

My flutter use case may be too pedestrian, but I have no issue with flutter using projects managed by nix.

I'm actually writing some Emacs Lisp right now, because I want $FEATURE in Emacs. I've been away from Emacs Lisp for awhile in the land of Clojure and I'm reimporting certain things the way they are done there.

Libraries that help with that, even though the major underlying structure isn't immutable data structures make Emacs Lisp bearable are: s.el, ht.el, dash.el It would be great if there was namespacing and less global state pollution.

Of course if you want to integrate with the rest of the Emacs ecosystem and you want some libraries that help you out make things nice means learning a whole different ballgame. Like wanting to use the great transient.el. That's super stateful and based on eieio.el. (Although transient.el is relatively good about hiding that behind a good API surface.)

Overall, even though I wish it was based on a functional core and Clojure's immutable data structure, concurrency, namespacing and its great EDN reader, I just accept the pragmatism on the human scale that if I want a great text based interface that interacts with the rest of my text driven workflow Emacs is a good choice and Emacs Lisp is acceptable.

That's a real 2022 response. Nowadays "Please let a LLM summarize the article for you, instead of wasting human time!" is the proper etiquette. ;-)

Cal also writes about reverse office hours. The idea is that instead of holding a 1 hour meeting where every person only has a small contribution to make (in the realm of 5 minutes or less), they don't attend that meeting but rather the person with the objective that needs input from several different players is tasked with going to the different players when it's convenient to the ones you need the small contributions from.

So I don't think Cal is only interested in optimizing his own life and dumping everything EFT style onto others.

Undoubtedly it was easier for Darwin to work 4 deep work hours a day because he didn't have to handle the kids, prepare the food, clean the house and mow the lawn and work in the garden. Based on having read Cal a lot I haven't seen him advocate this selfishness in the modern world.

I also pay for Kagi search and have a usage value of ~55% from what I pay and I'm fine with experiments.