Sony Pictures Entertainment will have no choice but to hold you responsible
Well, someone has to be responsible for Sony's massive fuckup and we all know it won't be Sony.
We've seen over the last year many open source, power in numbers projects have critical vulnerabilities waiting to be exposed. Those defects were sitting there for years, yet being open source didn't magically fix them.
I can't deny that - the "many eyes" argument hasn't quite held up over the years. However, the reason I prefer an open source solution is because they tend to acknowledge and fix the issue much faster than their closed source counterparts. Most of the serious security issues in open source software have a fix released within 24 hours. It takes many closed source organizations much longer than that to even admit that the problem exists. Worse yet, some vendors will deny the problem indefinitely or tell you to migrate to their new platform (which is obviously incredibly costly). With open source, you're free to fix the issue in-house or contract someone to do the work if the vendor is uncooperative.
Over the last year, I've learned that the key to internet security is that it doesn't exist.
That's the sad reality and it's completely independent of the licensing model of the software you use.
SAIDI: System Average Interruption Duration Index (average duration of interruption measured in hours)
SAIFI: System Average Interruption Frequency Index (average number of interruptions each customer experiences per year)
From what I gather, it's not *that* bad - most apps depending on systemd do so for the cgroups support.
That's the case now but soon desktop environments will start using logind and applications may start using journald. As systemd continues to offer more tightly-coupled modules, applications will likely start relying more on these modules until the point that systemd will likely be a requirement for almost all applications and desktop environments.