I couldn't agree more.
It really boils down to the simple fact that class loading in the JVM - for
the standard classloaders - is well-defined.
If a build tool is not able to reflect this, it is an unreliable build
tool. It doesn't matter if anyone thinks CLASSPATH order shouldn't matter
from
The date of Will Cohen's meeting is set: Sat, Oct 3rd, 13:00-15:00 UTC.
Please register to the meeting:
https://twitter.com/scicloj/status/1305227676731543555
On Friday, 11 September 2020 at 18:45:22 UTC+3 Daniel Slutsky wrote:
> We are planning a couple of meetings about Clojure in Geography.
>
I can't comment on the whole crazy world of JSON, but it's a shame to think
of all the coal-fired watts spent unnecessarily parsing UUIDs. If all you
need is a string, there is no dishonor in letting it be a string.
> I was made to wonder how the rest of the world lives!
>
> P.S. Also, never
I especially like the "bigger aspirations" -
https://github.com/cljctools/readme#bigger-aspirations
And your summary of relevant strengths of Clojure.
On Sunday, August 30, 2020 at 2:42:25 AM UTC-4, Sergei Udris wrote:
>
> Thought process behind and goals of the https://github.com/cljctools
>
Too fragile. This reminds me of the notion of "situated programming",
featured in the talk by Rich Hickey: you and your programs operate in the
middle of a bizarre and changing situation. For Clojure, the Java
ecosystem is part of that situation. Even if some jars do not overlap
today, you
