PD should hire some of these Google guys for their tree rendering!

In Android it isn't your job to kill off applications. They are supposed to sit there and eat memory when it is available. If you have 512MB of RAM, what is the point of having half of it empty just to make some graph in some resource app you have look pretty? Fill every bit of RAM you can with apps you are using or commonly use so they open quickly. When the system starts getting low on RAM and needs to free some, let Android send the app it wants to kill a Destroy command so the app can save its bundle and can reload that bundle when it is restored by you later.

I hope and pray for the day that people finally stop thinking having their RAM full is some bad thing no matter what.

My personal experience with older apps on iOS 4.2.1 is that they don't go to sleep nicely. They basically just close. Two examples I have of this are the Huffington Post and USA Today apps. If you leave them (say to change what you are listening to in Pandora) and come back via the quick app switching bar (double click home button) they will simply restart as if you just launched them. Other apps, like Twitter, deal with the switch beautifully. It is going to be a bit before iOS apps deal with multitasking properly.

As an Android and iOS developer your comments seem a bit misguided. As long as an Android device is properly responding to onPause() and onResume() there is ZERO reason an Android app should be eating resources in the background. There are no UI events passed to an application that is backgrounded on Android.

Zilch? Please use nil.

Google isn't your problem there man. Those videos aren't allowed due to the content creator. Right now the mobile devices don't support Google's advertising system on YouTube. So if you can't see the ads that overlay the video, you can't see the video.

This is actually why Google has been moving more and more of the apps in Android to being Market based rather than attached to the System. Examples would be Maps, Gmail and YouTube already. Screw the carriers and hardware mfg's not getting crap up to date. Just update all we can via the Market!

There are a lot of phones other than the N1 with official releases of Android 2.2:
- Droid 1
- Droid X
- Droid 2
- HTC Incredible (and its varients)
- HTC Evo
Just to name a few...

It is far more a victim of Google Voice Search on Android 2.2. The fact that I can say to my phone "Call Linex in Olathe, KS" and three seconds later it is dialing is simply to fantastic. The GOOG411 experiment gave them the testing they needed to make it a full fledge smartphone service that is only a small part of Voice Search.

Actually it only has a "kill switch" against unsigned /boot partitions. The /system partition is only signature checked after it is updated via the stock recovery partition. If you update things (or 100% replace) /system/ via something like Koush's Boot Strap Recovery that check never occurs. This is how some groups are working on getting AOSP based Android builds up and going for testing on the Droid X. As long as they can get it to work with the official /boot/ they are fine.

Also, it should be clear what the "kill switch" is. It isn't an eFuse like so many falsely said early on. The bootloader simply won't hand over to /boot/ and sits in a state waiting for RSD Lite to flash a new properly signed SBF to it.

I did a little looking to see how accurate this was and here is what I found:
MSN.com:
67KB Documents
84KB Images
286KB Scripts

Slashdot.org
121KB Documents
168KB Stylesheets
63KB Images
418KB Scripts

Digg.com
65KB Documents
60KB Stylesheets
378KB Images
240KB Scripts

Gmail.com (my Inbox)
931KB Documents
65KB Images
108B Scripts
1.33MB XHR

ps3.ign.com
168KB Documents
120KB Stylesheets
1.28MB Images
436KB Scripts

flickr.com
34KB Documents
5KB Stylesheets
165KB Images
2KB Scripts

cnn.com
172KB Documents
236KB Stylesheets
398KB Images
945KB Scripts

cspost.com
16KB Documents
9KB Stylesheets
266KB Images
98KB Scripts

So from this small sample that definitely seems to hold true. Most of these sites where script heavy and image light, though not 100% of the time.

Even though we have seen applications that say they are flashlights actually enable Phone Tethering get to the App Store? If you really think Apple is going over these things that finely, you are crazy.

15 of the 30 got on their list due to providing location data for advertising. I hardly consider that a sending your personal data as the article implies.

1) I never played the Eye only version, so I can't really speak to that.
2) The tracking is simply fantastic. When the wand transforms into an object in hand it never has missed a beat for us.
3) My girls are 2 and 4. Both of them play with it just fine. My 4 year old of course does a better job with the stuff that requires more fine control, but the 2 year old enjoys it all the same.

Hope that helps.

My kids already have three pets and they have most definitely cost more than the Move (crap, probably more than the PS3 + Move + TV combined!) ;)

But is it worth it? Not yet. The software that is currently there isn't enough to fully justify it or prove the platform. Having said that, I do believe it shows the potential to be awesome. Check out this trailer for EchoChrome 2:
http://www.youtube.com/watch?v=Usn6eo9FeTM
If Sony can get more interesting Move titles like this out, they will really have something.