Well, that's something anyway. Good job.

Look at it this way......cost us billions? No, we're going to borrow the money to pay for it, just like the high-speed rail in California.

Isn't that a bad thing? In California, we're never going to pay off the debt, so might as well build cool stuff while people are still willing to loan us money. It might not help much with CO2 output, but hey, we'll have cool new solar power plants.

ok, I'll ask you what I asked the other guy, is there anything you don't like about systemd, or do you like everything about it? Are you capable of thinking critically, or are you just another apologist?

The nutritional value is better than Ensure. It has less corn syrup, generally favoring complex carbohydrates over simple carbohydrates.

The biggest problem is they keep changing the formula, making it worse. In the latest formula, they doubled the amount of fat from 20% of the total to 40% of the total.

Who wants 40% of their diet to be fat? That's ridiculous.

I see.

Is there anything you don't like about systemd, or is all you can do defend it? Are you blinded into thinking that everything about it is good?

I think I understand what "portable" means.

You don't understand how to make things portable. I'm sorry, if you don't understand how to do it, that's your problem.

Do you think it's not true? Prima Facie it seems obvious, based on my own experience, and watching others.

In their case, it will allow them to switch vendors more easily.
Also, programmers write better code when they know people will be looking at it. The open source method for motivating better programming.

When things go right, you don't need the source code, but when things go wrong, you'll wish you had it.

Also, as to your gmail example, if the DoD plans on storing medical records in someone's crappy 'cloud,' they are giving themselves even more problems. You want to be able to control that data.

Wow fanboy, is there anything Lennart can't do? Is there anything he touches that isn't "brilliant?"

Seriously, you are handicapped because you don't understand architecture, so you can only repeat things you've heard. It's hard to have a reasonable discussion with you on this topic, because you lack the necessary skills. That's ok, not everyone needs to be a programmer.

Here is an example you should be able to understand, though. Your response will show whether you blindly worship at the feet of systemd devs, or if you are capable of thinking. As you know, there were some problems with cron, it didn't handle sleep very well, for example. When you have that problem, is the answer to rewrite cron completely, or to fix cron?

STFU? Anyone can insult, it doesn't make your point stronger.

So have I......so what? When Poettering writes straight code, it's pretty good. I would be happy to have him as a coworker. The problem is when he starts architecting, that's where he lacks skill. He would be wise to read some basic documents on the topic.

Then sometimes he makes amusing rookie mistakes. So that's where he is as a programmer: good code, poor design.

Thanks, I appreciate the concern. I don't make money based on my ability to use whatever software, I make my money designing good software. Although I've spent plenty of time studying systemd, so my career is safe.

btw, that points to the difference between people who like systemd, and people who don't. Those who favor it tend to look at the features, and say they are decent. Those who dislike it tend to look at the design, and say, "that's kind of wonky." A person can hold both opinions, they are not logically inconsistent. Unit files clearly fill a need people have.

I can read code. When systemd writes good code, I'll support it.

Regardless of whether they are starting with open source software, or closed source software........if I ever paid $4.3 billion for some software, I guarantee I would be getting the source for it. If the government pays that much for a system, one of the requirements should be that it ends up open source.

ok, so now I'm interested. You are clearly a strong proponent of systemd (some might even say 'fanboy'). What is it about systemd that you like so much? What are the features that really help you? What inspires your advocacy?

That web page is actually a disappointment. It is more like a list of every feature in systemd, as if it's trying to overwhelm you with data. It is highly unlikely that Debian switched because they liked every systemd feature equally, but that web page doesn't make clear which features they liked. Most likely there was a killer feature that made them want systemd.

And that is true, once you start digging in the forums, you find that they didn't like every feature equally, they liked simplicity of writing unit files over init scripts. That was the killer feature.