Perhaps -- but right now, it looks like the treatment may work best on people who have not been vaccinated.

In other words, the anti-vac population may have yet anotther reason to tell people not to get their vaccination.

I already pay Shaw (I'm in Canada) $60/month for a 10megabit connection. If I then have to pay Netflix extra money so that they can pay Shaw to allow the connection to run at 10Mb/s, then Shaw is double-dipping. If I've paid for 10Mb/s then I should GET 10Mb/s if it's technically feasible to do so.

Anything else is false advertising, contractual interference, and/or a Sherman Act violation.

If you don't have a problem with Hot Pockets, then you probably have a freezer section that borderline doesn't work. If a hot-pocket is nearly thawed when you throw it into the microwave, it will have pockets of semi-liquid that quickly heat up and help to thaw the internals which then heat up nicely. It doesn't have a whole lot to do with the power of your microwave.

The other solution is to run the thing on 'defrost' for a couple of minutes -- (a short blast of microwaves every 10 seconds or so, with time for the recently-heated liquids to thaw the area around them)... then follow the normal directions to get a properly hot hot-pocket.

Playing with large data sets is more of a pain in a spreadsheet ... and if they have 10K records now, it's not a shock that they'll grow to 100K in a few years. If you're designing for growth, then putting the break, today, at 10K is reasonable. Also, if you've got over 10K records, chances are that you will (eventually) be answering yes to some of the other questions -- like having multiple people doing updates and/or queries on the data.

That's part of the 'invisible hand of the market'. If I don't like the fact that you're pissing on my color/orientation/clothing style, I can refuse to do business with you and discourage my friends from doing so.

It's called 'leverage'. If you don't like it, you don't have to participate in the marketplace. ---- "rather than pissing and moaning about" people talking to their friends.

Touche. All European (and colonial) scientists shared latin. Scientists in other great cultures around the world just used their local 'universal' languages.

2.4million is 0.03% of their NET income in 2013. it's ... what, $.01 per customer per month??

10 or 15 years ago, that wouldn't have been something to take into account. A couple of people would have groused about it, and their friends might have paid attention, but the macro effect on the company would have been trivial.

Consider that Microsoft, for example, has gotten away with language like that in a piece of software that 90%+ of desktop computers are sold with, and that it's actually difficult to buy a computer without. Meaningful protests??? Roughly zero.

In this case, "legal' means "a court will rule that the clause as valid". Clauses that force you to go to arbitration rather than court (including class-action lawsuits) have been held as valid in the past -- including for things like software 'licenses' for purchased software.

This clause was pushing the envelope even further, and it's unlikely to have been held as valid (under these specific circumstances), but the fact that it's there might be enough to cause an unhappy customer to cave in and settle for less than (s)he might have in the absence of this clause.

The marketing debacle, on the other hand, isn't something that lawyers normally pay close attention to.

Yeah, but talk about proof that Caffeine can arrest development.

... and I bet that any kid that starts out this way is gonna be a mondo caffeine addict.

Anybody who states it that categorically is stupid, ignorant, full of hubris -- or setting up a straw-man.

The problem here is that people have been using the argument that Open Source is better because these issues can't happen "because" of the visibility.

Pretty much anything built by man is subject to errors. That includes source code -- open or closed. Any sane programmer knows this. The difference with open source is that the code is open to the users. Especially in the case of security, correctness is a high priority for many users, and those users can drive the bug-hunt process. As such, bugs tend to get found and fixed (sometimes proactively) faster with Free and Open Source code than with proprietary code.

For companies, on the other hand, security and correctness, in general, is a cost centre. It's often only pursued to the extent to which ignoring it affects profits. If it's considered better for the bottom line to ignore/hide a critical security bug than to fix it, then it may never get fixed. -- "Better for the bottom line" includes being paid to keep a bug open by the NSA/KGB/MOSAD/etc. The well-being of the customer base is only a (indirect) part of the profit calculation.

"Bad for the bottom line." Includes fixing code that you're no longer actively selling -- unless the bug hurts your public image too badly.

That's why, for example, XP is no longer going to be supported -- despite the fact that perhaps hundreds of millions of machines still use it.

Redhat 7.2 isn't officially supported by Red Hat, either -- but despite the fact that the current user base is probably in the range of hundreds or thousands, somebody who considers it critical infrastructure and can't/won't upgrade it can still arrange to get bug fixes because the source is legally available. RedHat isn't the gatekeeper for support the way that Microsoft is for Windows. RedHat is simply the (highly) preferred source of support.

Comcast has been messing with people's net feeds for a while now. People have been paying for N-Megabit connections and, to the extent to which those connections have been with NetFlix, those connections have been wilfully and needlessly degraded to well below N-Megabit.

TIme for a mass refund. period.

(also time for some law firm to make megabucks litigating this issue)

You can call 'protection money' whatever you want. It's still Extortion.

I don't mind the heads-up about a little-used piece of Gnu software (as pointed out, most distros push OpenSSL), but I do mind astro-turfing the Microsoft PR line of "Nobody's responsible if Linux fails!"

The irony, of course, is that most people haven't read Microsoft's EULA which effectively says 'Not only are we not responsible if Windows fails, but we'll sue you if you try to fix it yourself.'

This is really gonna bite the hundreds of millions running XP who will be orphaned this year when Microsoft stops supporting it. Not only do they face the prospect, in a matter of weeks, of never again seeing security updates from Microsoft, but it will be illegal to even try to fix future bugs themselves (or hire a third party to do it).

This last bit is something that Linux users have as a right

No support (not even 3rd party) for XP, and Windows 8 is just short of an entirely differend OS. You call THAT continuity?

At least with Linux, you have the option of (banding together with a group of like-minded entities, and) doing your own support, until you decide it's time to retire you old software/hardware combination.

That's the real choice and freedom you get when you use Free and/or Open Source software.

When Microsoft EOL's Vista (possibly as early as a couple of years from now), the people who tore their hair out getting used to it, are going to have to tear their hair out getting used to whatever Microsoft is shoving down people's throats then -- irrespective of whether or not the Vista based systems they have are really ready to be retired.