Skip to content

docs: compare LogIt++ with C++ logging libraries - #128

Open
LimiNode wants to merge 5 commits into
docs/information-architecturefrom
docs/comparison
Open

docs: compare LogIt++ with C++ logging libraries#128
LimiNode wants to merge 5 commits into
docs/information-architecturefrom
docs/comparison

Conversation

@LimiNode

@LimiNode LimiNode commented Sep 8, 2026

Copy link
Copy Markdown
Owner

Summary

  • add an English canonical comparison page and a Russian translation
  • compare LogIt++ with spdlog, Quill, Boost.Log, glog, and IceCream-Cpp
  • explain IceCream-Cpp as a diagnostic introspection utility rather than a logger/sink framework
  • document trade-offs and library-selection scenarios without presenting an unverified universal ranking
  • keep performance claims limited to the reproducible LogIt++/spdlog benchmark fixture
  • wire the canonical page into README, quickstart, Doxygen, and publish smoke checks

Validation

  • checked upstream release references and documentation links on 2026-09-08
  • git diff --check passes
  • generated page smoke coverage includes comparison.html

This PR is stacked on the documentation architecture work in #125 and should be retargeted/rebased onto the release branch after #125 lands.

Document LogIt++ trade-offs and design differences against spdlog, Quill, Boost.Log, glog, and IceCream-Cpp. Keep the benchmark section limited to the reproducible LogIt++/spdlog fixture, provide English and Russian pages, and wire the canonical page into Doxygen and documentation smoke checks.
Describe glog's stream-oriented macro surface without implying a printf API that the checked release does not document.
Keep the new comparison page in the same Doxygen documentation list as the other guides.
Keep the comparison link and feature summary as distinct Doxygen sections for a clearer generated landing page.
Align the English and Russian comparison pages with the checked upstream capabilities. Cover Quill named values, rate limiting, structured output, and Prometheus support; distinguish formatting and telemetry models; clarify Boost.Log queues, glog lifecycle, and LogIt++ storage semantics.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant