News for hackers. Stuff that matters.
Re:Clojure, the Good Parts by arohner on Tuesday April 19, 2016 @01:34PM (#11528631)
Author here. I agree, Timbre is new, and has some rough edges, but in my projects, I've found them worth putting up with. In my current project (18k LoClojure), I think the only serious dependency I have that uses j.u.logging or SLF4J is Datomic. Timbre has an interop library that will pipe java logs through timbre.

I agree knowledge of how Java logging works is still useful, but I'm not willing to be part of the problem anymore :-)

Agreed on Schema, and how it illustrates deficiencies in the type system. I still want core.typed, or something like it, but it's too immature for production use.

Re:Clojure, the Good Parts by ddellacosta on Tuesday April 19, 2016 @01:41PM (#11528676)
Totally understood re: timbre and not being a part of the problem of the Java logging ecosystem. I'll play with it again next time I have a chance and see if the interop lib can't solve some of the issues I had before.

Yeah, the post you folks put out on core.typed last fall (https://circleci.com/blog/why-were-no-longer-using-core-type...) was certainly disappointing but not unexpected...I'm curious to see if Jaunt goes anywhere at this point too: https://www.arrdem.com/2016/02/22/clojarr_-_a_friendly_cloju...

Anyways, thanks for the piece!

Re:Clojure, the Good Parts by twic on Tuesday April 19, 2016 @04:52PM (#11530299)
Can you ELIAJPWKVLAC* why Timbre is so much better than, say, Logback? I imagine not having to write XML configuration is one thing, but what else?

* Explain Like I'm A Java Programmer Who Knows Very Little About Clojure