Clojurians Log v2

Hi @wout.neirynck! This channel only accepts one submission per project per month, see channel description. For more updates, you can use the #releases channel. Thank you! 🚀 (You can leave this message for this time)

Ah didn't know that, thanks

This looks very useful, well done!

love your use of Clojure interactivity in your videos as a way of explaining/demoing your libs

I'm looking for information on the dataspex plugin. https://cdn.jsdelivr.net/npm/scittle@0.7.27/dist/scittle.dataspex.js does not exist (404) -- should I be doing something different to use it?

@timothypratley dataspex like some other plugins like hoplon are not included in the standard build, you can get those when you include them on the classpath and build scittle yourself

See here for more info: https://github.com/babashka/scittle/tree/main/plugins/demo

Thanks. I think it would help adoption if there were more pre-built options available. One idea is that there could be one or more alternative distributions: 1. scittle-contrib - builds all known plugins 2. scittle-official-full - builds all official plugins It would be valuable if these were automatically created whenever a new scittle is released. What do you think?

the reason I support plugins is that I don't want to include the whole CLJS ecosystem in my build

😄 right - I'm suggesting separate builds.

sure you can start scittle-contrib if you want :)

👍 cool, Thank you. Conceptually, is it sound?

note that you can't build optional plugins apart from the rest, everything is always one build

I'm already building scittle twice because of the dev files

conceptually it's sound. hoplon also has their own scittle distribution

Great. I'll give it a try and get back to you.

(moved further discussion to #scittle )

Scittle tooling is very hot right now. Well done!

Appreciate the 👍’s above, was helpful to see that this is maybe a common question. I’ve just updated the Trove README to make it immediately clearer who Trove is for and how it relates to Timbre, Telemere, etc.: > Trove is a minimal, modern alternative to https://github.com/clojure/tools.logging. > It’s intended for library authors that want to emit rich logging without forcing their users to adopt any particular backend (e.g. https://www.taoensso.com/telemere, https://www.taoensso.com/timbre, https://github.com/BrunoBonacci/mulog, https://github.com/clojure/tools.logging, https://www.slf4j.org/, etc.). I’ve also added a specific section re: structured logging: Why structured logging? The key difference between traditional and structured logging? • Traditional logging outputs strings (messages). • Structured logging in contrast outputs data. It retains rich data types and (nested) structures throughout the logging pipeline from logging callsite → filters → middleware → handlers. A data-oriented pipeline can make a huge difference - supporting easier filtering, transformation, analysis, etc. It’s also usually faster, since you only pay for serialization if/when you need it. In a lot of cases you can avoid serialization altogether if your final target (DB, etc.) supports the relevant types. The structured (data-oriented) approach is inherently more flexible, faster, and well suited to the tools and idioms offered by Clojure and ClojureScript.

That's a great addition; thanks!

Since you maintain both, which one would you recommend to most people?

@gentkr Hi Gent, Timbre and Trove serve different purposes. Trove is more for library authors that want to do logging and let their users choose a logging lib of their choice (like Timbre, Telemere, mulog, etc.). These days I’d recommend: • https://www.taoensso.com/trove for library authors • https://www.taoensso.com/telemere for everyone else (modern successor to Timbre, same API as Trove) But will continue to support Timbre, so folks happy with Timbre can continue to use it.