You may have missed the main point.

One fueling station 400 miles from the dealership and the car only has a range of 300 miles. Do the math.

That is why certain groups like fuel cells so much more than electric cars. You can still sell the nice hydrocarbon fuel stacks to get the hydrogen. And even though you generate carbon dioxide from reforming natural gas to hydrogen it is also significantly less efficient than just burning the gas directly. In fact a CNG car would probably use less gas per mile than these fuel cell cars will ultimately end up using.

It's also a way to ensure that GMO seeds can't spread beyond their intended planting and coincidentally would resolve a major issue with GMO approval in Europe.

Damned if you do, damned if you don't.

Binary is encryption? Wow, won't the NSA be happy to know that.

So develop an alternative to udev support and be happy in your contribution to linux. Oh wait, you expect other people to do this for you.

So your solution to bugs is to blow your foot off and delete the package? Are you serious? In the real software world we fix bugs, not declare the software worthless and delete it. It should be noted that the "bug" you've declared as catastrophic enough to warrant deleting the package could in fact be a debian bug and not a systemd bug. Ever considered that?

And that's the problem with this entire issue. You aren't interested in fixing bugs, you want to dictate to the rest of the community that we can't use the software if we want to.

This wouldn't be a systemd thread without a RedHat conspiracy. You need to go back on your meds, RedHat has done more for free software than anyone on the planet.

You are missing the OP's point, anything systemd does is wrong. It doesn't matter if it does the right thing or follows an RFC, it just means those things are wrong. He expects that if the right thing is what systemd does then the wrong thing should be done, in other words the system should boot and corrupt all the disks. Because clearly that's a better solution than systemd being right.

It could easily be avoided by the anti-systemd crowd developing and supporting alternative packages that support the required functionality. Gnome is only dependent on cgroups, not systemd. Unfortunately consolekit the only software outside systemd to support cgroups died in 2012 (the upstream died completely in that there were no active developers). To break the Gnone-systemd dependency the only thing needed is software that offers cgroup functionality, yet for two years no one stepped up.

The only Unix like system that uses SysV init is openBSD. Every other unix like system has their own init which offers similar functionality to systemd and is tied to features in their kernels that make use on other kernels impossible without massive feature porting at the kernel level. This is the most specious argument you could make.

The single biggest indictment of the anti-systemd crowd isn't that it will fail and waste everyone's time and eventually be replaced. It's that it will succeed and other software will come to depend on it. That's not a rational objection.

Telecommunication like any last mile utility service is a natural monopoly. The infrastructure build out costs are so much and the pay off time so long that competition is naturally discouraged. Not only that but the first person in the market can put such heavy economic pressure on an over-builder that it is almost impossible to get investment money to do so.

Ma-Bell was broke up about 30 year ago, the baby bells were encouraged to enter each others markets. In that time with free reign to do so how many of the Baby Bell's overbuilt into each others territory? What you suggest is simply so unlikely that it's laughably stupid. Only in the urbanest, wealthiest, densest areas of the US will you ever see an over builder under the best of circumstances.

You blame the lack of competition on government manipulation but you ignore or deliberately downplay the reality of free markets is that they naturally move towards monopolies. This is especially true in markets that are naturally inclined to monopolies because start up costs are so large. In these markets without government regulation costs will go up rapidly and quality will go down dramatically. An over builder attempts to enter the market and the monopoly provider simply provide predatory pricing in the areas where the over builder offers service.

You want good quality service at a low price? Then we do like every other western country, we regulate a monopoly provider. All the industrialized countries except the US have heavily regulated monopoly providers that provides regulated pricing to consumers and business. What we have in the US right now is totally unregulated markets where everyone is paying to build out the market 2 times and the one or two providers that exist jack up prices to their maximum limit and shut down all maintenance spending and milk the existing infrastructure for every dime before abandoning all the unprofitable areas.

There is one simple rule in a free market, without regulation the market will not remain free.

The battery life is good enough for the primary mission which is to plunge a drill into the comet. After they've accomplished the mission they will probably try something, but give them time to analyze things and accomplish the primary goal before they try.

Keep in mind they try to jump and they might jump into deep space.

Not if the server is using TLS, most do these days.

You are rejecting TONS of valid email. At least I was when I did the same thing. The problem with FQDN is that tons of major businesses using servers with invalid FQDN's or relay it through other servers that don't match the FQDN of the sender. I don't get a lot of spam because of my filtering measures but when I toggled FQDN on in postfix I started tossing 80% of my valid email. Major hosts such as Amazon couldn't send to my server because they have hundreds of randomly named relays sending our their automated messages. After my experience I realized that with VM's and the way things are setup now at most places FQDN filters are damn near worthless. There are far better filtering methods.