And yet you don't have that pesky rooting problem, meaning that users have no way around the policies you need to enforce. Not to mention being able to enforce firewall policies that ensure your company data isn't accessible to any app. (Heck, you can even restrict them to a whitelist of allowed apps if you want.)

Even the partial root exploit found for the PlayBook has been corrected - and no new root is in sight. (Good thing since this is the foundation of their new platform.)

As far as suckage -- I'd suggest taking a look at BB device made int he last couple of years - and certainly the new BB10 is shaping up to be promising, as it's a completely clean break from the legacy OS.

Alternatively you have implemented additional design patterns without knowing it.

That's something I've seen a lot - just because someone doesn't know a name for something doesn't mean that they can't use it. In interviews I've asked people to explain the factory pattern (arbitrary example) to me - and had them draw blanks. But a few questions reveals that they're familiar with it, and just never associated it with the name "factory pattern".

Um, no. The commentary in this case was the second hand blog article - which starts speaking of drones, kill lists, etc - and not the original artist's commentary as far as I know. (Though someone who speaks Dutch could confirm it.)

A low uid just means they got here first. Frankly I'm surprised that someone with a low-six uid hasn't realized that already ;)

I would argue that if you need yet another layer to simply track the location of errors in a browser-based environment, you've Done It Wrong.

Thepoint is that this won't stop them from trying- and imposing more draconian measures. After all, it never has before.

How about actually clicking "search anyway" when prompted with the popup? You'd see that it actually searched anyway and turned up the term in question.

Probably because in the US there's no Chinese government sitting between you and the loading of your search results -- unlike in China.

Because none of those words have the same starkly emotional impact across such a wide demographic.

Can the cloud-based world succeed in a world where ISP/carrier bandwidth caps/overages are become prevalent?

Holy crap, it's too late -- they've already done it.