This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (81)
- # boot (1)
- # cider (1)
- # cljs-dev (15)
- # cljsrn (1)
- # clojure (26)
- # clojure-europe (9)
- # clojure-hamburg (2)
- # clojure-italy (6)
- # clojure-nl (6)
- # clojure-spec (10)
- # clojure-uk (33)
- # clojurescript (9)
- # clojurex (5)
- # cursive (14)
- # datomic (21)
- # devcards (2)
- # duct (72)
- # figwheel (1)
- # fulcro (6)
- # kaocha (3)
- # leiningen (5)
- # nrepl (10)
- # off-topic (65)
- # parinfer (12)
- # re-frame (68)
- # reagent (1)
- # reitit (14)
- # shadow-cljs (65)
- # spacemacs (6)
- # sql (4)
- # tools-deps (2)
- # yada (1)
IDEs are great…. but I just opened a project, made my code change, committed and pushed - and IntelliJ is still indexing the project… 😄
At ClojureX this year we have a panel session as usual. Rather than just be my curation, please reply as a thread if there are speakers you would like to see on the panel this year.
Oh behave yourself @jr0cket all the talks look great. I’m really looking forward to it.
@thomas no, your heckling is merely emotional scarring, not the reason I leave the building 🙂
Heckling of any form other than chanting "We love Jase" with a loving tone with be met with stern and sustained hugging, from both myself and @U0525KG62
Warm and positive hugs are freely available from myself and @U0525KG62, on your consent of course. If you ask us nicely we can also pair hug you.
Any recommendations for a (free) working space in London, with wifi and whiteboards ? Would like to do some face to face coaching with one of my students. Or if anyone is cool with two people hanging out in a corner of their office on Monday afternoon and talking about Clojure, then please let me know.
@cfeckardt Great to hear that it's useful! It's a bit of a funny story behind it... We started with
lein at work back in 2011 and switched everything to
boot at the end of 2015. Once we were on Boot, we moved our dependencies out to EDN files and had a
.properties file with all our "pinned" dependencies (shared across all the subprojects in our monorepo). When
tools.deps appeared, I wanted to align our tooling with that new "standard" (we were already using
deps.edn as our filename, but with a different format). So I wrote
boot-tools-deps thinking I'd just swap the format over and continue using Boot...
...but in the end we decided to completely switch to the new CLI and
deps.edn, so we're not actually using
boot-tools-deps now 😐 But! Our dev/test/build pipeline is much simpler (and faster) now. We no longer have to deal with weird edge cases caused by Boot's "shadow filesystem" abstraction and the asynchronous classpath refreshing stuff in pods (both of which had caused us pain).