
Building #ElectricClojure and https://xitter.cf/t.co/JkYr6J4dpu. I believe in excellence, and I believe that many others do too. Baháʼí. https://xitter.cf/t.co/aBmRZmuoCs
🌎
Joined May 2009
- Tweets3.1K
- Following3.2K
- Followers4.6K
- Likes16.2K
First update to my list of product management aphorisms in years! The previous #1 aphorism, "Assumptions are what gets you killed", the killer of 99% of startups, has been dethroned for an even more fatal bias, Hubris, the downfall of all great men. In the words of Feynman:
Screenshot of a web-based object navigator targetting the JVM management interface, to reflect out the process classpath and navigate into the contents of an uberjar. This application is defined in about 200 lines of Clojure (.clj) for the java reflection (for some simple parsing and weaving together of a set of queries that relate but were not intentionally built to relate), and absolutely no frontend code. The navigator UI is fully abstracted away by a saas, the UI is not in the same process as the JVM being interrogated, it is remote. They talk via a reverse websocket with the Electric wire protocol. For more info see clojure.net/ "Network your REPL", a new experiment from Hyperfiddle.
Lightning talk! A Datomic Entity Browser for Prod — Clojure Conj 2025 #ElectricClojure
Replying to @MaineFrameworks @fresheyeball
serious answer: tiktok. completely filled with his stuff
Here's one just from this week, i've started writing them down
clojurescript compilation error, cannot resolve ::hfql keyword alias, but the line with the error is :clj-only. Why does ClojureScript even see this? The fix is to :require the namespace with :as-alias in clojurescript, even though it is never used. The impl detail is something to do with how the reader works, I forget, and it doesn't matter, what matters is my users face errors like this all the time







