IMO until the abstract logging interface is built into the language, or standard library, we'll keep building different log libraries and adapters between them, and shipping libraries without logging.
It makes me actively disinterested in these libraries. I just want some built in interface with levels, hierarchy, and structured logging
Never really caught on with the idea of integrating external I/O in something as fundamental as logging. More often that not a pull vs push approach is suited for logging. There are dozens of high performant log collectors/aggregators who can collect, transform, and push logs to N number of stores. What’s the advantage of doing this right inside the app? (Besides maybe serverless functions?)
It’s frustrating that this is necessary but it definitely makes sense, and I will probably add it to several projects soon.
Thanks for your hard work!
Makes me think of the big tent philosophy of Grafana Alloy for OTEL
Where does log layer fit into the broader ecosystem?
Situation: there are 14 competing JS logging APIs.