😼 mogge

Moaning ☕

Good moaning

How is everyone after the weekend?

in need of coffee

how about you

Good moaning indeed @yogidevbear ...

Finished my second cup of coffee

morning

I’ll go brew some

Morning @otfrom 👋

morning

good morning.

has anyone tried ring with 1.9.0-alphax ?

trying to find out if there is a branch for that

basically, trying to run gorilla-repl with 1.9.0-alpha16, and it complains because a spec in ring doesn't conform to a given spec for ns'es

apparently it's really due to 1.9.0-alpha16 according to changelog https://www.clojure.org/community/devchangelog

i’ve been using ring fine with 15 for a while, not tried 16 yet

interesting, moving spec outside core sort of

anyone know if there’s any write-up on why?

oh, it’s right here below

@elise_huard We’ve been using Ring with all the 1.9 Alpha builds. Which version of Ring are you using?

@seancorfield I'm now suspecting I landed in dependency hell, in that running the plugin seems to be requiring an older version of ring-core (1.2.2)

so have to work that out, PEBCAK probably 🙂

Ouch! Yeah, that’s old. We’re on 1.6 I think…

yes, explicitly requiring 1.6.1. oh well ...

You’ll need :exclusions on something else to force it not to use the earlier Ring. lein deps :tree will be your friend there. Or tell Leiningen to be :pedantic true I think (I’m a Boot user so I’m not as familiar with Leiningen now).

@elise_huard I'm not sure if anyone is on #gorilla but it might be worth asking

@otfrom: ooh good call

@seancorfield thank you!

@seancorfield out of interest, does boot makes it easier to debug these kind of issues?

@elise_huard I don’t think it makes much difference on the basic stuff like dependencies (although you can easily configure global exclusions — not sure if lein supports that?) but I find the dynamic nature of Boot much easier to work with in a REPL-based development workflow.

For example, Boot makes it easy to dynamically add new dependencies while you’re working (without restarting your REPL), and it’s much easier to write new tasks for Boot than it is to write new plugins for Leiningen.

that is definitely a big win!

We (World Singles) switched from Leiningen to Boot about 18 months ago and now almost our entire dev/test/build/deploy pipeline is written in Clojure using Boot. So that’s our biggest win.

We’ve externalized all our dependencies (into EDN files) and we manage versions across projects using a properties file, and we have a Boot task to load source code and analyze namespace dependencies dynamically to construct the overall dependencies and versions for any given subproject we’re working on.

nice one! might be worth another look for us (you had me at dynamic reloading of dependencies in the repl to be honest 🙂 )

our deployment is fairly hooked in continuous integration, but would be interesting to see if some bits could still be replaced by boot tasks