// the take
XCGLogger is a logging framework for Swift that adds structured console/file output (timestamps, file, line, function) on top of plain print() calls, with a destination/filter/formatter architecture for routing logs to multiple targets. It's aimed at iOS/macOS/tvOS/watchOS developers who want NSLog-style context without writing their own wrapper.
The destination model (console, file, Apple System Log, custom) with independent log levels per destination is genuinely flexible for apps that need different verbosity in different places. Closure-based log calls mean expensive string interpolation is skipped entirely when a level is filtered out, which matters in hot paths. AutoRotatingFileDestination handles size/time-based rotation and retention out of the box, which most teams would otherwise hand-roll badly.
Last push was mid-2024 with no Swift 6 / strict concurrency story visible, and the README's own To Do list still lists Objective-C and Linux support as unaddressed years later - this reads as largely done, not actively maintained. It predates swift-log, so anyone building a library (versus an app) that wants to interoperate with other logging consumers will have to bridge it manually. The userInfo-dictionary approach to tagging and dev-attribution is explicitly flagged by the maintainer as 'experimental' and a bit awkward to use, and colorized output in Xcode itself has been broken since Xcode 8 dropped plugin support - you only get ANSI color via terminal/file output now.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →