That battery will NOT last forever,

And neither does an internal combustion engine, either. Your point?

and when it needs a new one you'd be better off scrapping the entire car and buying a new one.

Citation needed. Seriously.

How good is that for the environment?

Awesome, actually. The battery can be recycled, and there aren't any heavy metals to deal with either.

--
BMO

Never go full retard. X is not even remotely as important as init. For one thing, if X dies, who will restart it? And do we really want computers that explode when the GUI dies? I, for one, would like network services to terminate gracefully. The whole idea of TCP/IP networks, the dominant network used with Unix, is peer-to-peer. I may well run both services and clients on my machine. If X dies, the clients may die (if they're not text and running in screen) but the servers won't.

So the argument is that since the kernel is complex, we should add more complexity, or that more complexity won't matter? That's an ignorant, illogical argument.

Systemd still has to be more complicated so that it knows how to run these other processes, which wasn't even necessary. init was never meant to manage daemons. daemons were meant to manage themselves, or be run from inetd. If you want more complexity, inetd is the place to add it. And for handling daemons which don't adequately manage themselves, there's daemontools. There was simply no need whatsoever for this to happen.

It is bad, because PID1 is now responsible for a bunch of things which could have existed in any other daemon. And rather than roll the things which actually make sense in together, everything is getting rolled together. So now not only do we depend on a complex kernel, but we depend on a needlessly complex init system. There was no good reason to put all of this stuff into the same daemon.

Yes, yes I can. And I did.

Does nothing a script can't do

Systemd doesn't even fucking use capabilities, just cgroups. Which we could use before systemd. Systemd manages permissions in lieu of using capabilities, e.g. apparmor or selinux.

No. That is the virtue. They are simple. Simplicity is still a virtue.

Making PID1 more complex makes everything more fragile and opens up security holes.

NIH

This is making init do stuff it doesn't need to do, which makes it more complex, which makes it more fragile. You should not need a detailed explanation to understand why this is a bad thing.

Lifting which should not be done by PID 1. And PID 1 has to be more complex than it should be just to handle those external programs.

It does a lot of stuff the init system shouldn't do.

cgroups existed before systemd.

Up to the init script.

Already handled by several init systems.

We call it inetd.

That is ignorance at best, or perhaps a lie.

You have no idea about anything, that didn't stop you. I see why you didn't log in.

So to be clear, it's more awful to have 1 out of every 9 people have to pass two people if they want to use the bathroom than to have 2 out of every 6? Because that's typical economy seating plans are 3-3.

It's not a religion, it's a principle. When it makes sense, you put it aside and get work done. The argument against systemd is that it doesn't make sense. systemd is a simple case of NIH because it provides absolutely nothing which could not be implemented with the existing daemons and some small shell scripts.

That's right.

That's not the complaint. The complaint is that the process at PID 1 should be simple. You people running around screaming about a bunch of different processes are only compounding the proof that you do not understand Unix. It's not a problem to have many processes.

Bullshit, they're still letting licensed commercial vehicles use the HOV lane. The fact is that HOV lanes are shit. They're a waste of space which accomplishes none of the stated goals. Simply adding another general lane does more to reduce emissions, because it does more to reduce congestion, and thus reduces idling — where vehicles without start-stop systems get 0 MPG and thus are producing pure pollution. They're always trying to justify the existence of HOV lanes with bullshit like this, but they still are unjustifiable.

The headline says farmers. The text says farm workers. Very much not the same thing. A farmer is the owner of the farm. A farm worker is generally a hired hand, often (though not always) a migrant, and if so typically from Mexico or farther south.

The story suggests that the multi-drug-resistant bacteria are the result of antibiotic treatment of the animals at the farm. This misses another possibility:

In Mexico, most antibiotics are over-the-counter, much like asprin here in the US. People who feel ill or have some infection often buy and take them. Typically they use them until they no longer show symptoms - then stop, rather than taking a full regimin and killing off all the bacteria. (Why take more of the non-free drug once the symptoms are gone? Waste of money, right?) This is a recipe for creating drug-resistant bacteria.

Of course if an infection is resistant to one antibiotic, a paitent is likely to try another, and another, and so on until they find one that works. THAT's a recipe for maintaining and improving the bug's resistance to the front line antibiotics while breeding resistance to others.

As a result, a substantial fraction of the workers arriving from south of the Mexican border are carriers of multi-drug-resistant baceria.

Meanwhile, a farming operation is likely to give a limited number of antibiotics continuously, so non-resistant infections are wiped out before they can develop resistance, and if they do develop resistance it will be to the particular drugs used, rather than the universe of antibiotics.

Of course, infected workers can infect livestock, just as livestock can infect workers. And infected workers can trade infections around, just as livestock can. (More so, since the livestock tends to be kept separated, to reduce both disease spread and breeding by unintended pairings, limitations that farmers can't impose on their workers - and would be unlikely to try even if they could.)

So it seems to me that responsible researchers would go a bit farther before reporting: Like by doing genetic testing on the strains of bug in the various workers and the livestock, and running models on the results to try to identfy whether the bugs are from the herd or the workers.

I don't see any such work alluded to in this popularized reporting. It seems to just assume that the bugs were developed on the farm and spread to the workers. I hope this is a disconnect between the actual research and the report, rather than an accurate characterization of the research.

Phones have big screens now, so they need armor anyway. So since you're going to put armor on the phone, you want the phone to get thinner, so that the phone with a case on it is still thin. Just making the phone thin allows the user to put whichever case on it they like, so they get to personalize their phone and you don't have to try to anticipate their needs, instead letting the whole world do that. And that's why having the camera really doesn't matter. In fact, having the bezel around it protrude from the camera probably helps protect that side from scratches. What's the problem, planned to slot-load the phone?

Is there anything in this whitelist?

The fact You refer to "4chan" as a "notorious hacker" shows Your interpretation should be presumed erroneous.

And your reading of his message is erroneous, because it was reported in the media that the notorious hacker was indeed "4chan."

--
BMO

No, no I don't. I have electricity, but I get water out of the ground and have gas brought in on a truck.

Right. Because someone is charging for something, they're not permitted to use the lane. That's prejudicial, since both people who are not charging and people who are charging but have a license to do so are able to use the lane. So it's not ANYONE, it's ANYONE YOU APPROVE OF.

Real animals have traction control.