The issue is logs are suppose to be text. Seriously, wtf. You some Poettering fan boy or something?
Having the logs twice is saving space, got it. Do you hear yourself?
Yes, and many distros have that out of the box... But they don't have it sent to keep the binary journal as close to empty as possible. So you end up with twice the space in use for logs. As for the issue with binary logs, text logs can be read by far more tools and utilities, rather than just journalctl and pipes.
By itself, solely doing init, it would have been fine, however, binary logging (even if you eventually end up with a text log, that's wasting disk space on a binary format no one wants or needs), and it didn't stop there. He keeps replacing Linux subsystem after subsystem, and many of those replacements are not progress, just duplication of effort and creates more ways for configuration drift.
It is ridiculous. Nothing like says f you to a large percentage of your user base like pushing out a solution that doesn't work for them.
More like over baked but still only half done.
Wayland is set of protocols.
Oh my god! It's like hearing the same on hold greeting again and again. WE KNOW!
Oh you had me going in the first half. Sly devil you. Wayland still doesn't work on the fleet of equipment we have.
no...nonono... AHHHHH! - Vegita DBZA
That's what somethin' somethin' said lastnight, Trebek! ;)
As Microsoft and Poettering intended.
Standard updates on RHEL can sometimes break yum / dnf due to updating python.