This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-30
Channels
- # aleph (4)
- # announcements (5)
- # architecture (1)
- # aws (5)
- # babashka (12)
- # beginners (143)
- # chlorine-clover (4)
- # cider (16)
- # clj-kondo (44)
- # cljfx (26)
- # cljsrn (2)
- # clojure (34)
- # clojure-europe (28)
- # clojure-gamedev (1)
- # clojure-nl (3)
- # clojure-provo (2)
- # clojure-spec (6)
- # clojure-uk (17)
- # clojurescript (99)
- # code-reviews (6)
- # core-async (15)
- # cryogen (9)
- # cursive (14)
- # data-science (1)
- # datomic (16)
- # duct (1)
- # events (4)
- # exercism (1)
- # figwheel-main (3)
- # fulcro (3)
- # hugsql (7)
- # leiningen (4)
- # malli (15)
- # off-topic (13)
- # pathom (8)
- # re-frame (7)
- # reitit (35)
- # remote-jobs (1)
- # sci (10)
- # shadow-cljs (32)
- # sql (5)
- # tools-deps (102)
- # tree-sitter (3)
- # uncomplicate (7)
- # vim (40)
- # xtdb (8)
I'm considering running a babashka questionnaire in December to learn what people are using babashka for, what they find lacking or redundant. If you would like to feature a question in the questionnaire, please respond in thread.
Whether implicit printing of the last evaluation in the script to stdout should be enabled by default
Is the intention that it's a kind of safety net, i.e. "you forgot to do something with this value"?
In a #!
interpreter for a general-purpose language, I don't think there's much precedent for doing it. But then again, many of them aren't functional/expression-based.
I'm slightly worried that with org.httpkit.client some people will run into the issues that it consumes the entire request / response into memory. I hadn't seen those issues before I added it and people were mostly positive about httpkit. Maybe people don't do huge requests mostly? cc @alekcz360
yeah, for small use cases it's super handy and IMO if you build something big enough that it needs to be optimized you could probably stand to make a clojure project out of it