Yeah, I only buy new cars and houses - and when I'm done with them, I just give them away. Selling used items is pathetic.

Yes, the subject of the poll was formed similarly to the subject of an email. Call the Grammarnazitechnichforceschwizerstein!

Looks like the UK beat Michigan to the punch.
http://slashdot.org/story/11/04/19/2231240/michigan-police-could-search-cell-phones-during-traffic-stops

...except if it's public or otherwise willingliy disclosed, in which case there's no reason to prevent employers from accessing the information. Such prevention is, IMHO, a bad idea, as it introduces the possibility of accidentally breaking the law (say a prospective employee connects with a first-stage interviewer on LinkedIn before the second stage of the interview process, or the prospective employee becoemes friend of a friend of the CEO - or just a fan of the company - on Facebook).

I can tell you that there's no better employee than one who overstates his accomplishments to the point of very nearly outright lying. Yessir - that's the kind of person who's a joy to have as a coworker, and a joy to manage.

I presume that the vote was cast for Skynet, or at least against some relative of John Connor?

Weird. When I search Google for "android custom shader", I find a bunch of sample code which doesn't ever mention specific graphics hardware capabilities. But I supposed I can take your word for it. It's a shame that Google failed to provide a portable API for games (well, a shame for someone - I don't care about games on cell phones). It's also a shame that this problem experienced by "all game developers" hasn't led anyone to write a library yet.

You got a code example or two, or are we just going to argue theory? I've never specicially programmed for Android, but I've written Unix (not just Linux) apps and web apps for quite some time, and I know that there are a whole lot of bad programmers out there in both areas who often blame the devices instead of learning specifications. So, I'm understandably skeptical when some no-name developer says "it's too hard to support all these devices" - especially when their application is not in any way technically demanding, and when somehow thousands of other developers are almost certainly getting by without owning one of every Android device out there.

If it's actually true that any Android developer actually must physically own hundreds of devices to test upon, then yeah, the testing cycle in development is clearly impossible, and the platform can't possibly succeed. But the platform is succeeding somehow, so I'll need an alternate explanation as to how that can be.

I don't really use a mainframe often enough to be statistically significant; pretty much all of my computing is done on personal computing devices.

You mean "if only developers would use the APIs instead of insisting on going around APIs to directly access lower-level hardware", I think. Or are we supposed to believe that every other developer who has an Android game also has to have an army of test hardware just to make their product work?

So, when presented with "6*3" do you really do 10*3 from memory and then subtract 3 four times? It seems like it'd be a whole lot easier to remember 6*3 to begin with. :)

Well, Jefferson was a dick.

University Police are no more "cops" than mall cops or anyone else dressed as "Officer Sexy" at a Halloween party.

Not that I trust cops either, but Paul Blart there is no cop.

You might try getting a portable computer made in the last 20 years; they've come down in weight since the switch to LCDs.

Sprint tethered cell phone plan FTW!

/uses ~8GB/month, no throttling, no extra charges