> Is there a bug report with a dismissive reply? Or one being ignored?

That's always my reaction to blog posts like this as well. A blog post is not a bug report. Given the mentioned bug in the systemd/syslog interaction that made it into RHEL, there should be a bug in the RHEL bug-tracker, and I'd hope it'd be a high priority one.

I think the issue is just stability in general. I just moved to a new server recently, and I decided to go with CentOS 6 instead of 7, as people were reporting that CentOS 7 is just a little less stable in general than 6. (Although systemd probably isn't entirely responsible for the lower stability in CentOS 7, it probably is one of the major changes in CentOS 7 so it likely takes a good share of the blame).

You always end up with bugs in released software, even CentOS. Some bugs only show up in certain situations, and might be difficult to track down. The only way to give a good guarantee of stability is for a large number of people to use the damn thing for years on end!

If systemd had no ill will towards syslog, there would be no journald.

No, journald has its own benefits. Creating an alternative to some software doesn't mean you have ill will towards it.

A compatible alternative to syslog would have been healthy. An incompatible that is the only thing properly supported by systemd is not.

I don't know why you're being downvoted. can someone enlighten me?

you're not allowed to dislike system-d nowadays.

seems like every time I make a valid point against systemd it's flagkilled instead of being replied to.

I've taken to lurking on #systemd in order to see when they sound the bells for an HN thread takeover.