Linux

Short version: some people (I'm one of them) object to systemd on grounds that are 75% philosophical and 25% the kind of tech detail that's more of a matter of taste than anything else. The older sysV init is a smaller program, which means that it has a smaller absolute number of bugs than systemd but also does less on its own. Some of us regard "does less" as a feature rather than a bug.

If systemd works for you and you don't know or care about the philosophical side of the argument, there is probably no benefit for you in switching.

Uhm, it's Systemd.

I think this guy has a few points.

You should embrace systemd. It's actually good. Replaces all startup scripts, logs to a common log, even has scheduled systemd jobs just like cron but better, since they can have proper dependencies. Want to run something right after network stack is up and working? Easy with systemd, more difficult with cron and more hacky.

For average users, it's a matter of preference. Like asking what's the benefit of chocolate over vanilla.

You are curious though, so I'd recommend giving another init system a try. That would give you some perspective on systemd.