Especially as the gist of the theory is: anthropogenic global warming leading to climate change. (And the shift is sensible. If the global average temperature increase didn't lead to climate change, we wouldn't be that concerned with it).

That we don't use that mouthful all the time is no different than you lot calling para-acetylaminophenol, acetaminophen, and we calling it paracetamol. The full thing is just too much. It's just basically a name. The underlying "thing" is still the same. In both cases.

True. Those of us who were "there" remember when he didn't think it was that big a deal to develop the kernel using proprietary tools, esp. source code control systems (can you say "Bitkeeper"), and couldn't understand why everybody was whining about the risks.

We all know how that ended. It blew up all in the kernel developers faces. However, it also meant that he sat down and started writing git, and as a result we're all now better off than where we started.

So have faith. Either he's right, and systemd will not turn out to be that bad, or his faith in systemd will end in tears, and then, he'll sit down and write a new startup management system that will kick everybody else's collective asses!

In either case, we win! :-)

I look around and see a lot of news coverage of this story.

Which means a lot of you have been breaking the first two rules of bacteria club!

Of course it has effect. There's such a thing as being too easy. Now, Jan Freese, the former head of the Swedish data inspection authority wrote a very good book on the subject, many, many years ago (in the mid eighties if memory serves), which unfortunately is in Swedish, so it won't do you much good. But one of his main points was that the existence of information isn't the main problem, but that manual barriers to its processing is.

It is my opinon that its become too bloody easy to find out too much about people today, for no good reason. In the important cases (not hiring child molesters at the day care) the data is still there, and still accessible for the concerned parties. That's not a problem. That everybody else should have access to the same data at the drop of a hat, needs to be argued. "Just because we can" isn't much of an argument.

So no. My original argument still stands. The data is there, no-one is arguing that is should be redacted. But that's not to say that the barriers to automatic processing should necessarily be as low as humanly possible. There aren't just benefits, there are risks as well.

P.S. And "information doesn't want to be free". If it wants anything it's to be $4.95, but even that is giving it much too much credit.

Of course you can find them. What do you think libraries are for? Just a place to get free WiFi?

I swear, kids today wouldn't have survived fifteen minutes in the eighties...

No its not. No-one is suggesting that the officially archived court proceedings be retroactively redacted. (Or the officially archived copy of the newspaper in question be redacted either, for that matter).

The public records are sacrosanct and still preserved.

Sure. Perhaps you've heard of bigamy? Alice can't marry Carol because Bob already has a vested marital interest with Alice. For example, if Alice marries Carol and dies, Carol is entitled to 100% of her assets as spouse. But so is Bob.

That's not the policy rationale for the prohibition on bigamy, and while it is perhaps a little better of a reason than administrative convenience, it boils down to the same thing, since the question of marital property is one of the issues that legislatures will have to address when the ban is overturned as it inevitably will be.

On the contrary, tradition is absolutely relevant as to whether something is a fundamental right. Marriage is a fundamental right because it's enshrined in our traditions and collective conscience. ...
Polygamy does not have such a place in our traditions or collective conscience, and therefore is not a fundamental right.

Yep, that's the bullshit argument that people were rolling out against same sex marriage all right. That because it wasn't traditional, it wasn't fundamental.

The core mistake with that argument, whether in the context of same sex marriage or marriage among persons already married, or in larger numbers than two, is that what's fundamental is not opposite sex marriage, or same sex marriage, or polygamous marriage, but simply marriage, without qualification of any kind.

Issues like gender, race, consanguinity, marital status, and number of spouses are all restrictions on that singular fundamental right. Whether they stand hinges on whether they can be justified. Two of them, it transpires, cannot be. Ultimately I think the only restriction that will hold up will be consent, and perhaps consanguinity will have to be reframed in terms of consent if it's to be salvaged.

because, as noted earlier, 3>2. Equal protection is an issue where two groups that are equally situated are treated differently. For marriage, there is no difference between a gay couple and a heterosexual couple. There is a difference between a couple and a larger group, however.

The litigant needn't be the entire group. Marriage is a fundamental right, subject to various restrictions, such as consent and consanguinity. Yesterday, one of the restrictions, at least in some places, was that the genders of two of the spouses couldn't be the same. Today, it's fine nationwide if they're the same.

The restriction to look at now is whether the marital status of each spouse in the marriage at hand is single. Today it has to be. But there's not a good reason for it. (As already mentioned, administrative convenience is not a good reason). So why can't Alice, who is married to Bob, now also marry Carol? Bob isn't marrying Carol; the A-C marriage would be between two people only. You're treating Alice differently merely because she is already married.

It's also not a fundamental right, as polygamy is not part of the traditions and collective conscience of society, except for Mormons.

Marriage is a fundamental right and is extremely broad. Restrictions on marriage, such as requiring the spouses to be of opposite genders, or of the same race, or of the same religion, or of compatible castes, etc. are not inherently part of marriage and are certainly not part of the fundamental right of marriage.

Also, today's events make it clear that tradition is irrelevant; polygamy is practiced today among many groups, and has a long history back into antiquity. Same sex marriage was known in the past but was far more rare.

It will certainly be a massive pain in the ass. But administrative inconvenience is not an adequate justification for denying people their fundamental rights or equal protection of the law. It'll take a while, but just as this took a while, but in time polyamororous marriages will be legally recognized.

"My god... It's full of Liefeld!"

I think we're missing the real story here.

The article is suggesting that Java update _actually works_ and is capable of _updating Java_.

I can't remember the last time that was true.

That's okay. If nobody else likes it, more dogshit for you.

So you have proven through scientific study that some people are allergic to the colour red. Where's the problem there?

That would be when you click the "No, not now! I'm in the middle of giving a presentation to the board!" button, and then it responds with "Well, FINE. I'm tired of waiting and next time I WON'T ASK YOU."

Or when you don't respond quickly enough and it takes your lack of response as consent.

And then it decides to reboot on its own.

Surely there must be a way to have avoided this.

Maybe Microsoft should set up some kind of... Lab. To certify the Quality of Hardware for Windows. And maybe they could make it really simple for vendors like Samsung to send them copies of drivers for certification so that Windows Update would be aware that they existed.

And maybe, instead of demanding millions of dollars in fees for this service, they could charge something simple up front like just $250 and then not cause any more problems. Then Samsung would have been able to run through a quick certification process and avoided all of this trouble.

Man, why does Microsoft make it so hard for vendors to get their devices supported?