Controversy is nothing new when it comes to systemd. Many people find this new Linux init system to be inherently flawed in most ways, yet it is still gaining traction with major distros like Arch Linux, openSUSE, Fedora, and soon both Ubuntu and Debian GNU/Linux. The adoption of systemd for Debian 8 "Jessie" has been particularly fraught with strife and animosity.
Some have described the systemd adoption process as having been a "coup", while others are vowing to stick with Debian 7 as long as possible before moving to another distro. Others are so upset by what they see as a complete betrayal of the Debian and open source communities that there is serious discussion about forking Debian. Regardless of one's stance toward systemd, it cannot be argued that it has become one of the most divisive and disruptive changes in the long history of the Debian project, threatening to destroy both the project and the community that has built up around it.
(Score: 2) by tonyPick on Sunday September 28 2014, @11:14AM
TINFOILHAT WARNING:
That _is_ a bit tinfoily. I'd agree that it's a lot harder to audit the systemd codebase, and that certain security agencies will *love* the opportunity to sneak in a bit of malicious code there and get it to own the entire system, however RH aren't necessarily in need of any further motivation than owning the core integration, and (by extension) being able to monetize a bigger slice of the market, control the direction of development, and keeping Oracle and Canonical on the back foot is a definite plus.
(And hey, if I worked at RH I'd probably be busy convincing myself the whole "integrated modular platform" thing was a good idea too: It'd be developing tons of the shiny cool "stuff", and probably solving problems I actually had in the process).