If you create the product yourself you don't need an accountant until you sell it.
It should be obvious to anyone that RedHat has a vested interest in making the vast majority of Linux distributions dependent on technology it controls. Linux is its bread-and-butter.
It appears RedHat has realised that, through systemd, it can readily provide preferential support for its own projects, and place roadblocks up for projects it does not control, thus extending its influence broadly and quickly. By using tenuous dependencies amongst its own projects it can speed adoption even faster.
Once it has significant influence, and the maintainers of competing projects have drifted away either out of frustration or because they are starved of oxygen, RedHat knows that they can effectively take Linux closed-source by restricting access to documentation and fighting changes that are not in their own best interests.
At this point, they can market themselves as the only rational choice for corporate Linux support -- and this would be perfectly reasonable because they would have effective control of the ecosystem.
Linux (as in a full OS implementation) is an extremely complex beast and you can't just "fork it" and start your own 'distro' from scratch anymore -- you would have to leverage a small army to do it, then keep that army to maintain it. It's just not practical.
At the same time, Linux has matured to the point of attaining some measure of corporate credibility, and from RedHat's point of view, it no longer needs its 'open source' roots to remain viable. RedHat also, understandably, fears potential competition.
Through systemd and subsequent takeovers of other ecosystem components, RedHat can leverage its own position while stifling potential competition -- this is a best-case scenario for any corporation. It will have an advantage in the marketplace, potential customers will recognise that advantage, and buy its products and support contracts.
I hope you can understand why many see this as an extremely compelling case. Arguing that RedHat has 'ethics' and would 'never do such a thing' is immature and silly -- RedHat is a corporation, it exists to profit from its opportunities, just like any other company. To attempt to argue that it would not do so is contrary to what we can assume is its default state.
It's no 'conspiracy theory' to assume that a corporation will behave like a corporation; arguing that it is just makes one look like a naive child. systemd is one large step toward RedHat gaining the ability to reap what it has sewn -- for its benefit and not necessarily ours.
While you may think of your examples as 'advancements', many people (myself included) do not.
Your examples also do not affect the way a headless server boots. systemd does. And not in a good way.
Whether one dislikes systemd or not isn't necessarily because of what it does or doesn't do. The issue for many people (myself included) is simply that it's a monolith that keeps trying to grow larger in an "open" world that was meant to stand for a certain amount of platform agnosticism and component independence.
I realise that systemd can make life easier for some more novice users but to be true to the spirit of the open source community I would expect it to be optional where it can be so. When it starts to intrude into critical areas and make itself mandatory in some releases, that bothers me. It makes me think that the whole business is a sneaky attempt to subvert the Linux kernel and eventually take control of Linux as a whole.
Totally agree. He sees what Linus has and wants it for himself. The problem with that is, as you point out, Linus did what he did because he wanted to run UNIX (well, Minix?) on a POS old PC. Poettering really just wants the fame.
I live here, it's awesome =)
Seriously though, South Australia, while having a reputation for being a "backward" state, is actually one of (if not the) most liberal, progressive states in Australia. Adelaide has a cool startup culture too!
It's a pretty niche app, but the Slashdot crowd has a pretty large percentage of retro-computer collectors, so I thought it might be worth a mention...
tapDancer is an Android app that encodes
...have been around for years. I know they don't generally share the road (except with hapless interlopers who have to get out of the way) but there's still been much knowledge gleaned there. So the 'science' is already eay more advanced than with autonomous cars, for example.
...think that was ever going to last? C'mon now... really?
Firefox better watch itself. Trying to "nudge" people into creating apps that only work properly with their browser / OS may not end well for it.
While I agree most digital pianos do not have the greatest sound, VST plugins (particularly Kontakt) can emulate a piano quite closely using libraries that are gigabytes in size. It's not uncommon to see a MacBook chained to a digital piano during a performance.
there are virtually no stop signs, only round-abouts and "give way"s (yields). Never mind cycling, DRIVING is much quicker!
Uber is set to meet with the Directorate next week but it is likely the demands the Directorate will place on Uber drivers, such as mandatory criminal record checks, vehicle inspections and insurance, will make the service in Melbourne unviable.
Meanwhile, the New South Wales government is awaiting a report to determine if Uber drivers operating in that state are doing so illegally, warning that drivers could face substantial fines if they are found to have been operating in breach of the law. In South Australia, it doesn't even appear Uber will get off the ground — the state has made it clear that those who operate as an Uber driver will be driving without being covered by the state's mandatory insurance coverage, essentially de-registering their vehicle and making them liable for fines and license suspension."
Link to Original Source
Unfortunately, while still theoretically possible, installing an alternative init system means doing without a number of useful, even essential system programs. By design, systemd appears to be a full-blown everything-including-the-kitchen-sink solution to the relatively simple problem of starting up a Unix-like system. Systemd, for example, is a hard-coded dependency for installing Network Manager, probably the most user-friendly way for a desktop Linux system to connect to a wireless or wired network. Just this week, I woke up to find out that systemd had become a dependency for running PolicyKit, the suite of programs responsible for user privileges and permissions in a typical Linux desktop.
I was able to replace Network Manager with connman, a lightweight program originally developed for mobile devices. But with systemd infecting even the PolicyKit framework, I find myself faced with a dilemma. Should I just let systemd take over my entire system, or should I retreat to my old terminal-based computing in the hope that the horde of the systemDead don't take over the Linux kernel itself?
What are your plans for working with or working around systemd? Are there any mainstream GNU/Linux distros that haven't adopted and have no plans of migrating to systemd? Or is migrating to one of the bigger BSD systems the better and more future-proof solution?"