i'm also behind RMS on this one. GNU works well, why change from something that works to what we already know that leads to other kinds of issues.
I hope GNOME devels don't permit this.
There are two situations with chronic health problems - one where a person has been on a health insurance plan and paying it, and one where they haven't.
In the first case, their payments to the insurer were the expected value of their health, essentially - if they had a 1% chance of getting cancer that cost $100,000 to treat, they would be paying roughly $1,000 for the insurance - simplified of course, but it's the basic premise. So when they happen to be in the 1%, it doesn't matter, because that's what they paid for, and yes, it fits the insurance model.
When someone hasn't had insurance and has a chronic condition, though, it's more like asking someone to insurance a house that has already been washed away by a flood, and is built three feet from the water. There is a 100% chance that the insurer will have to pay more than they take in from the customer. If the insurer is forced to take these people in, the affected person must be subsidized by the rest of the insured. They are not paying the expected value of the cost of their care, because the probability is such that they *cannot* pay the expected value of their care. This is no longer insurance, it is charity. The closest working model that still looks like insurance would be, essentially, "insurance insurance" that everyone has to start buying to pay for the ability to continue buying insurance after you would stop being eligible for it. But again, that doesn't work for the people who haven't been paying that fee to begin with.
My point being, trying to buy insurance *after* you get an expensive disease is the same as buying car insurance after you crash, house insurance after it burns down, or life insurance after you die. Insurance is about balancing possible future payments, not certain ones.
Let me guess: You're having an impossible time finding that guy with fifteen years programing experience, with five years experience on that niche program your company uses, a Master's degree in Computer Science, who needs no assistance relocating, willing to work 60+ hours a week, for $70,000/yr + crappy benefits?
There's TONS of talent out there right now. Get your H.R. person out of the resume-screening job and be a little flexible with candidates and you'll find them.
People seem to forget the context of that "undermining the peer review process" took place.
They certainly tried to impact the peer review process. The paper in question resulted in half of the editorial board of the journal in question resigning over the peer review process that took place.
The paper in question turned out to be underwritten by the American Petroleum Institute.
As for Mann and Jones' apparent effort to punish the journal Climate Research, the paper that ignited his indignation is a 2003 study that turned out to be underwritten by the American Petroleum Institute. Eventually half the editorial board of the journal quit in protest. And even if CRU's climate data turns out to have some holes, the group is only one of four major agencies, including NASA, that contribute temperature data to major climate models — and CRU's data largely matches up with the others'.
So they are going to deploy the ability to remotely update the users device. Because the bad guys will never figure out how the company does it. I can see it now. An entire carriers smart cell line bricked by a remote exploit that updates phones.
I would much rather have an ARM netbook than that POS Atom and its power-sucking chipset anyway. Especially if it ran real OS X and not a stripped iPhone-like OS tied to that obnoxious app store.
I'd happily run Linux or BSD on ARM as well though. I don't believe in x86-everywhere. x86 sucks, it's just had enough R&D dollars thrown at it to make it fairly quick and cheap to produce. Hell, I'd much rather Apple had stuck with PPC.
I think a better solution would be for the patent to be described using pseudocode or some variation thereof. Since this is afterall a software patent, the application should be written in a form that is legible to others in the field. It would also lead to easier settlement of a dispute since previous art could more easily be compared with pseudocode.
1 1 was a race-horse, 2 2 was 1 2. When 1 1 1 1 race, 2 2 1 1 2.