Yeah, these people never do their research. Its very easy to find the discussions and reasoning the devs had at the time.

That especially disqualifies the conspiracy idiots who come up with myths about Red Hat or Poettering or Microsoft or so puppeteering Linux into its dooooom

Nah, the issue is accidental corruption, different parsers doing things differently, stuff like that. Happens often with “mostly text but actually some structured data also” formats, doesn’t happen with formats that have well specified framing.

Because most people prefer it. Again: having a minority taste doesn’t mean you’re oppressed when there’s an option to have what you want.

Read. I’m saying that you lied, not that your preferences are bad.

Systemd doesn’t force you to use binlogs.

Can you add more fields? Is there no ambiguity in context switching? No breakage around whitespace?

If so, sure, that’s fine then.

WTF. Saying “it uses binlogs” as if that wasn’t a choice is just a lie. I called it out. Deal with it.

Right, that happened to me too.

And it’s a problem 100% unrelated to systemd, so I wouldn’t count it here.

That old load of bullshit again. You could swap out the logs if you want a shittier, less searchable (but text based) logging system. The rest can be countered in a similarly conclusive way, and has been repeatedly in the last decade or so.

Inform yourself before copy-pasting misinformation and misleading propaganda.