Cu29_log, a Fast Structured Text Logging in Rust

Log better. Solve problems faster.

Hello, Some time ago I did a data logger for fun, just to check if I could beat the performance of an old C++ project of mine (mini-async-log) and to avoid letting my multithreading-C skills rust when on a non-programming gig (using Yocto/OE, very little programming). This project is a BSD licensed, producer-wait-free (when using thread-local storage) generic message logger with high performance, decent test coverage, and type-safe C strings (requires C11 or C++ compiler). It was a shame to let this project to die unknown, as I think that it has potential to be used on some niches as…

I've just released rust-loguru, a logging library for Rust that aims to combine intuitive API design (inspired by Go/Python's Loguru) with Rust's performance characteristics. Some highlights: - Consistently outperforms the standard log crate by 50-80% in benchmarks. - Multiple log levels and an extensible handler system -File rotation with better performance than log4rs and other alternatives - Error handling utilities and context helpers I built this because I wanted a logger that was both ergonomic to use and high-performance. The benchmarks comparing it to slog, log, and tracing are…

Tabs, splits, and tmux work fine until you have several projects open with logs, tests, and long-running shells. I kept rebuilding context instead of resuming work. Horizon puts shells on an infinite canvas. You can arrange them into workspaces and reopen later with layout, scrollback, and history intact. Built in 3 days with Claude/Codex, dogfooding the workflow as I went. Feedback and contributions welcome.

We made a VS Code extension [1] that lets you visualise logs and traces in the context of your code. It basically lets you recreate a debugger-like experience (with a call stack) from logs alone. This saves you from browsing logs and trying to make sense of them outside the context of your code base. We got this idea from endlessly browsing traces emitted by the tracing crate [3] in the Google Cloud Logging UI. We really wanted to see the logs in the context of the code that emitted them, rather than switching back-and-forth between logs and source code to make sense of what happened. It's a…