We aren't all "good at coding," but we know what init system we want.

We aren't all "doctors," but we know we don't want vaccines.

We aren't all "scientists," but we know global warming is a hoax.

I cannot be the only one sick of seeing this crap posted over and over. systemd is being implemented in distributions because a) it is good and b) the people making that decision are the ones qualified to do so.

I would like to, but first we have to educate some of them.

See, the thing is that enough of us are convinced that women are valuable contributors that we want to prioritize their education and get them into the job market so that we can evaluate real world performance. Right now, attitudes like yours are making that difficult.

That's correct. ISC dhclient, the standard on GNU/Linux distributions, will not renew a lease if it attempts to get one and does not get a response. That might happen if a site loses power and the internet connection is not up when power is restored and the firewall boots. Or if the link is down long enough for dhclient to attempt renewal while the link is down.

PulseAudio - OK, yes. Clearly desktop oriented.

CUPS - we still need print spoolers. Especially in environments where accounting and chargeback are required. The old print systems were harder to set up than CUPS. This is needed on servers just as much as it is on desktops.

NetworkManager - I used to manage a lot of firewalls that ran CentOS. NetworkManager was nice, because sites where the internet connection was not 100% reliable and not static could disconnect the uplink Ethernet cable, and plug it back in to renew DHCP. Without NetworkManager, they had to power cycle a system with R/W mounted filesystems. That sucked, a lot. NetworkManager also has a place on servers.

It's been exactly two weeks since Slashdot discussed one of several studies that conclude that groups with more women perform better than groups with fewer. Already, readers here seem to have largely forgotten that. It should be pretty obvious why there's a demand to recruit more women into the industry.

What the fuck is it with design people acting like their profession is the only one there is?

There's a whole world of professional work to be done for design on the web, in mobile apps, etc that doesn't need CMYK.

No.... it doesn't. Not as far as I can tell. None of the spec sheets I can find list Thunderbolt. Your coworker's Ethernet adapter is almost certainly USB.

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.