This is today's fun: https://github.com/BetterThanTomorrow/calva/issues/1585

(And it is also a bit fun, because the test safety net grows as I am chasing the bug down using tests.)

Fixed it now. Will probably release in a moment. Rest of this Calva day will be spent on quality in this area of Calva.

Congrats! This means you will have more budget to spend on Clojure OSS as well ;) ;)

🙂

that’s a lotta dinero

My wife has one of them M1 Air and it sure is a great computer. Maybe you can buy a used one?

I guess I could

But I also want to have 16GB of memory :)

Maybe I could just buy one and spend 1600 euros ...

Compared to a Pro machine it's still quite cheap ;P

The m1 macbook does have 16GB. I guess it’s harder to find a used one with 16GB, though.

exactly

I still find it incredible that my personal M1 macbook air performs better than the top of the line 16" intel macbook pro I’m working on now 😛

:)

I guess I could shift the older M1 model to my wife once her Macbook Pro 2015 wears out, she usually only uses it at her desk ...

Sounds like you have a plan! 😃

a new air will come out this year likely

likely m2

I am trying to convince myself it's a good buy, but I have a hard time justifying the move for my use

https://www.macrumors.com/2022/03/08/kuo-macbook-air-2022-m1/

The 16GB Macbook Air is a joy. Unconditional yes for me, the value is the same and the prices will probably go higher with, ahem, the situation (the war in Ukraine).

war??? I think you mean “special military operation” 🤡

placed the order ... do you think compiling binaries for M1 are compatible with newer processors for mac, m2, whatever? or does every processor need its own toolchain/CI? that would be quite the struggle

Pretty sure there's only one arch- I haven't seen anything like this (multiple toolchain needs ) previously.

I wondered if I should get the 1TB drive and pay 200 euro more compared to the 512GB one... but for a secondary laptop this is already a pretty luxurious purchase. So I dug down with ncduon my old Macbook Air and discovered a lot of junk and now have 200GB free of 512GB, so I guess I'm good with 512GB

https://twitter.com/borkdude/status/1501859484456689664

I'm loving the cute small charger!

Also, less weight to carry on a trip!

It's really nice! Tomorrow daycare is closed so I'm taking the little one to the grandparents for the day. I can put in a day's full coding + meetings without even having the charger with me.

@U04V15CAJ You got it already? Congrats.

Yeah, got it in the mail today

oooh yes... I wouldn't want to pay for it myself of course

Thomann is the MVP in germany for all things music & audio. Their physical store is also very nice, almost campus-like

Is it located in Berlin?

No, more like northern Bavaria

Should work well with thread-first, shouldn’t it? That’s what we did in beginning with testcontainers, before we had a wrapper:

(-> (org.testcontainers.containers.GenericContainer. "postgres:12.2")
                       (.withExposedPorts (into-array Integer [(int 5432)]))
                       (.withEnv "POSTGRES_PASSSWORD" pw))

I'm trying but it doesn't quite work like that 😞

(import [org.simplejavamail MailerBuilder])


  (-> (MailerBuilder/withSMTPServer "server" (int 25))
      (.buildMailer)
      (.sendEmail my-mail))

I'm a 🤡

@javahippie I presume that will work with doto as well as each of those methods just returns the mutated object?

though I suppose only trusting the whatever is returned from the method is a safer bet than expecting the original object in the fluid builder to be mutated

The withSMTPServer returns a stateful builder which would also work with doto, but the “buildMailer” method has a different type as a response.

so -> is probably "safer"

Let’s just say in that builder there are some interesting design choices 😉

caveat developer

I have a function lying around that takes class and uses reflection to generate a function taking a map of options in kebab case and builds with it

I'm trying to avoid reflection if possible but still … post the gist :)

I couldn't find it, but this is the gist of it, example for Ben Mane's Caffeine

(let [opts (gensym "opts__")
      builder (gensym "builder__")
      builder-opts (keep
                    (fn [{:keys [return-type flags name parameter-types]}]
                      (when (and
                             (not (:static flags))
                             (:public flags)
                             (<= 1 (count parameter-types))
                             (= 'com.github.benmanes.caffeine.cache.Caffeine return-type))
                        [name parameter-types]))
                    (:members (clojure.reflect/reflect (Caffeine/newBuilder))))
      chain
      (mapcat (fn [[m [arg]]]
                (let [k (csk/->kebab-case-keyword m)
                      met (symbol (str "." m))]
                  (if arg
                    `[(contains? ~opts ~k) (~met (~k ~opts))]
                    `[(contains? ~opts ~k) ~met])))
              builder-opts)]
  `(cond-> ~builder
     ~@chain))

The builders return an instance of the builder itself with the new values attached, then it depends if the original object is stateful, or built “on the fly”

well, thanks for expanding that photo slack

clj or cljs?

@javahippie clj

I use clj-http for everything and it fulfills all my JSON and Transit needs. But I wonder if there is a CLJ client which makes use of Javas native HTTP client

I came across a really weird error today; no idea if it's related, but it was also a weird behavior with the def form. https://clojurians.slack.com/archives/C87NB2CFN/p1646846870791379

hmm - perhaps related - in both cases it seems some compilation has happened in between the evaluation of the body of the def form version and the call of the 0-args fn version which changes the environment unexpectedly

in your case a concrete method is defined and in my case it looks like a record class is recompiled

that will let us get rid of some nasty js code in our gulpfiles which serialises js datastructures as EDN (to send to shadow as config)

awesome. let me know if you have any questions. there is also an #nbb channel