This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-12-08
Channels
- # adventofcode (15)
- # aleph (2)
- # announcements (1)
- # beginners (5)
- # biff (18)
- # cider (2)
- # clj-commons (13)
- # clj-kondo (7)
- # cljs-dev (7)
- # clojure-europe (23)
- # clojure-ireland (1)
- # clojure-nl (1)
- # clojure-norway (7)
- # clojure-spec (3)
- # clojure-uk (2)
- # cursive (21)
- # emacs (3)
- # honeysql (1)
- # humbleui (7)
- # hyperfiddle (6)
- # introduce-yourself (1)
- # london-clojurians (1)
- # nbb (8)
- # overtone (3)
- # re-frame (15)
- # shadow-cljs (12)
- # squint (12)
- # tools-deps (1)
- # xtdb (1)
Something else that's been bothering me, overtone uses a mix of println and java logging. I don't think using a real logging framework makes much sense here. There's some benefit in being able to up the verbosity, but because Java logging it's such a mess it's also unpredictable. I noticed for instance that in minibeast the logs don't show up. I don't want to help someone debug their logging setup first before I can actually get some debug info... It also writes a log file under .overtone. has anyone ever looked at that? When would that be useful?