In #548 (comment) @JohnTitor brought up the broader question of what to do with the list of integrations listed in the README. They're currently presented as "the most popular" implementations out there. Right now the list isn't really curated that way; if there's a new crate that integrates with log then we add it to the list.
The function the list serves is giving users a kick-start to get actual data out of log, which on its own simply pipes your events into oblivion.
Alternative strategies to achieving that function are:
- Linking a Cargo keyword for
log or logger as mentioned in the linked comment.
- Updating the wording of the README to not suggest the list is curated in any way besides listing libraries that integrate with
log. It's up to end-users to evaluate the suitability of these libraries for their own needs.
In #548 (comment) @JohnTitor brought up the broader question of what to do with the list of integrations listed in the README. They're currently presented as "the most popular" implementations out there. Right now the list isn't really curated that way; if there's a new crate that integrates with
logthen we add it to the list.The function the list serves is giving users a kick-start to get actual data out of
log, which on its own simply pipes your events into oblivion.Alternative strategies to achieving that function are:
logorloggeras mentioned in the linked comment.log. It's up to end-users to evaluate the suitability of these libraries for their own needs.