This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-15
Channels
- # announcements (1)
- # asami (29)
- # babashka (31)
- # beginners (48)
- # calva (39)
- # cljsrn (4)
- # clojure (56)
- # clojure-dev (51)
- # clojure-doc (3)
- # clojure-europe (40)
- # clojure-gamedev (13)
- # clojure-italy (22)
- # clojure-nl (3)
- # clojure-uk (5)
- # cursive (9)
- # datomic (184)
- # events (7)
- # fulcro (8)
- # graalvm (2)
- # jobs (1)
- # malli (6)
- # meander (1)
- # nrepl (5)
- # off-topic (10)
- # pathom (9)
- # polylith (33)
- # portal (2)
- # re-frame (7)
- # reagent (12)
- # releases (3)
- # remote-jobs (3)
- # reveal (27)
- # shadow-cljs (34)
- # sql (1)
- # vim (7)
- # xtdb (62)
hmm I am the first person today here in EU and in NL and UK. Maybe I missed a memo or something :thinking_face:
This morning I got into character đ´ Scrubbed the balcony clean after a nightly đĽ attack. âDarn kidsâ in my đ§ đ´ during 𧚠𧽠. But now, â and đ¤ đť !
People shouldnât mess with other peopleâs stuff, regardless of their age. But they do. Thatâs why Iâm moving away from people as soon as I can.
morning !
Good morning đ
What dev dependencies had the biggest impact on improving your workflow ?
tools.namesapce
@U2DART3HA you use it to rename your namespaces or to reload them ? what's your main usecase ?
back in the day it was clj-refactor, especially the add-dep-to-project thingy, which I believe now is b0rken (thanks jdk 9+). deps.edn has something similar. It was basically invaluable when starting a new project.
My use case is:
- in a long running REPL environment (lasting weeks)
- where dependencies do not change
- I want to ensure my REPL state matches the source without restarting the JVM.
The need to reload almost always arises in two cases:
- before running tests
- during a meeting while screen sharing:
â hey G what's the value of foo
line 42 ?
â It's :bar
â may we see it?
â sure (press eval, :bar shows up)
â hey G this is confusing to me, either I misunderstood the spec or you did, let's ensure foo is implemented correctly.
â do we know if we touched any of foo or foo's dependencies during this screen sharing session?
â I don't remember
â so we can't look into foo before we are confident the REPL state is correct.
â right
â ok it's time to reload everything, retry to eval foo, only then we can dig into the code.
Thanks Geoffrey ! that is indeed very useful !
No big impact yet but I play with clj-async-profiler and/or criterium and with Reveal.
nice @U0522TWDA! do you know if there is a profiler that can generate some sort of report for all namespaces automatically ? without having to manually instrument every call ? the question isn't very well phrased for sure I can try rephrasing
http://clojure-goes-fast.com/blog/profiling-tool-async-profiler/ can profile "everything", just run prof/start at one point and prof/stop at another.
thanks !
Just another mandag morgen
Godmorgen!
mĂĽning!
Because that is the day when you can send kids out of the house and sit down to do some coding (while indulging yourself with đľ and secret đŞ ) đ
Morning! For the experimental minded, we have a babashka + native running tools.build + tools.deps.alpha version here. https://github.com/babashka/tools.bbuild
Guten morgen.
I was in Berlin last week and I missed the chance meeting some of the nice people from this channel. (Assumed somebody of your would live in Berlin). It should happen again thought, so I'm looking forward to that đ
Last weekend I met with @rahul080327 and another friend of his, he came over from Berlin to Amersfoort and is now on his way to a new job in London. He and his friend cooked for us in our home an Indian (vegan) specialty.