Kind of. Its license actually isn't compatible with the GPL, so there's a whole lot of Free Software developers that can't use it.

I think you misunderstood what you were told. Or they misunderstood something themselves. What you described is not true.

I'm mostly certain that what someone along the line was trying to describe was that if person X is applying for a job, and you contact their former employers to verify their work history, the former employers are only allowed to confirm or deny your employment. They cannot be used as references. If they give you any kind of feedback on person X other than confirming work history, they could be sued for doing so. That is why work history is listed separately from references.

Are you upset that I said not the same process instead of not the same binary?

Those things are handled by separate programs, entirely. Systemd is small tools, doing individual, well defined jobs.

Are you happier now?

I'm familiar with those. They're much better than what we used to have. In the old system, there was either a mountain of repeated code with minor differences, or there were templates that were modified with sed to create individual configuration files.

Maintaining the templates is far easier.

You are misinformed. Systemd is a project which provides a collection of tools. One of them handles daemon and system startup. One of them handles logging. One of them handles device node creation. One of them handles firewall rule management. etc.

Systemd is quite UNIX-y.

We already have that. Journald is optional. You can turn it off.

And that seems to be one of the big differences between people who like systemd and people who don't.

People who actually took the time to look at systemd more often like the design, and understand that the one project consists of many small tools.

Then there's a community of people who rely entirely on hearsay. They don't like systemd, but almost all of the things they don't like about it aren't true. In this case, believing that PID 1 is a process that does daemon handling, and logging, and firewall rule handling, and DNS, and device node handling, and...

Those things are not handled by the same process. It's non-monolithic. It's small tools doing individual, well defined jobs.

systemd is actually a lot of little utilities that each do one thing. If you don't know that, you're probably getting your information from biased sources.

You're welcome.

Firefox is also a smaller download, a smaller install, starts faster, runs JavaScript faster, allows plugins on the mobile version, and allows users to run their own sync server, compared with Chrome.

Mozilla's work is really shining these days. Firefox is a better browser by every metric I can think of.

...which is basically the only valid criticism in this entire thread. Google made one phone whose support ended too soon, mostly because the SoC vendor essentially went tits up.

Which is an excellent example for why Free Software matters at all levels of the stack, including firmware. Too many people fail to take that seriously.

Google's support policy is no such thing, but Google only sets the policy for the hardware that they sell.

I seriously cannot understand how naive this conversation is. If you buy a product from Company X, you are exchanging money for goods and services from Company X. It is their responsibility to provide you with goods and services.

It is not Google's responsibility to do the development, testing, and support for hardware from Company X for which they were not paid.

Google supports their phones for a very reasonable amount of time. If you want support, I suggest you buy one.

If that's what you want, then BUY A PHONE FROM GOOGLE.

Otherwise, you're expecting Google to provide the development and support for hardware they didn't sell. Your money goes to company X, but you expect Google to do the work? That's not how any economic system works. You made an exchange of money for goods with company X. Warranty, support, etc is their responsibility. They're the one that you're paying.

I was thinking the same thing. 3DES isn't deprecated because it's insecure, it's deprecated because it's SLOW. Its security is fine.

And like a typical IT guy, what you "know" is beyond question. No way you could possibly be wrong.

If, someday, you work with enterprise systems, you might come to realize that very large systems are often riddled with inefficiencies. When multiple parties are involved, or legal compliance, those inefficiencies can become powerfully entrenched.

Take a look at some of the high rated comments on this article for explanations as to why and how banking is not as efficient as you imagine.

Yep. Bought a Honda Insight this year. Unlike the Prius, it has all physical buttons.

Sadly, the Prius dominates that market segment, and the Insight is being discontinued.