This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-22
Channels
- # adventofcode (26)
- # aleph (34)
- # announcements (10)
- # babashka (71)
- # beginners (80)
- # biff (7)
- # calva (1)
- # cider (4)
- # cljdoc (12)
- # clojure (8)
- # clojure-belgium (1)
- # clojure-europe (11)
- # clojure-nl (3)
- # clojure-norway (18)
- # clojure-sg (3)
- # clojure-sweden (2)
- # clojurescript (18)
- # clojutre (4)
- # conjure (1)
- # core-logic (4)
- # datahike (1)
- # datascript (3)
- # emacs (27)
- # exercism (1)
- # gratitude (12)
- # introduce-yourself (4)
- # joyride (1)
- # lsp (46)
- # malli (3)
- # membrane (2)
- # nbb (1)
- # off-topic (3)
- # other-languages (7)
- # pedestal (4)
- # portal (3)
- # practicalli (1)
- # rdf (33)
- # re-frame (11)
- # releases (1)
- # ring (1)
- # scittle (34)
- # shadow-cljs (10)
- # squint (12)
- # tools-deps (89)
- # tree-sitter (2)
- # xtdb (14)
My internal monologue:
> oh, I didn't realize there was a membrane/autoui
namespace. That's an interesting namespace name, I wonder what it is? <skims, skims .....> blades.user/vice
? Blades in the Dark!?
I've found it's worth staying on your toes when digging in the membrane codebase 😆
haha, yea. My friend has this way over-engineered spreadsheet he uses to run his campaign. The idea was to takes some json that matched the campaign state and automatically generate a UI for it. Since he didn't know clojure, I was also trying to get it to run in the browser. Basically, it was trying to do too many things and I never really figured out the sweetspot between ease of use and flexibility. I still think the general approach is possible, but haven't had the time to revisit. I should probably just remove that namespace for now since it doesn't do anything.