I would totally agree with this. I'm often both the producer and consumer though, and the consumer side is painful enough I tend to avoid journald. From the p

I would totally agree with this. I'm often both the producer and consumer though, and the consumer side is painful enough I tend to avoid journald. From the producer side, I typically use a logging library/extension that handles its own log rotation and doesn't require logrotate. It's a half-dozen lines of code or so, not too onerous.