Or because the Apache license is a BSD style license that allows for this.

His technical assistant might have worked for Sony.

Yes, in his example at the bottom he is using a root shell, but the application (which is shown in the video) isn't running as root.

Ah, this will be the first NASA ship that won't be at the Cosmosphere. They have Mercury, Gemini and Apollo Capsules. They have a few Russian capsules (not sure which exactly). They have an actual Titan rocket even. To bad :(

I live 3 blocks from my office.

I picked up the 3DS on launch day along with Super Street Fighter 4, Pilot Wings and Super Monkey Ball. For myself I have no issue sitting down for 45 minutes+ with any of these titles and feeling fine afterwards. I will note that in both Pilot Wings and Super Monkey Ball I can't have the 3D slider all the way up. If I do the images start to cross and it messes with my eyes. This doesn't happen in Super Street Fighter 4, so I am not 100% sure what the 3D slider is doing differently between these titles.

I will also note that I have no issues with headaches or motion sickness from 3D movies at a theater or in home with active shutter glasses.

They didn't change the background, they changed the color temperatures of the AMOLED display.

And why can't you manage those same servers via an Android phone? RDP, Citrix, SSH, ect...all supported just fine.

Far from it. 2.2 brings the JIT compiler which offers some great performance boosts. This doesn't affect dev's in a feature sense, but faster phones are faster phones. 2.3 really only brought NFC to the API and right now, that doesn't do much for us. It did bring some new basic UI elements that look really nice, but again...that doesn't change my code or lock out 2.1 users.

Yeah, this whole fragmentation thing is just killing us Android dev's right???

Or not: http://developer.android.com/resources/dashboard/platform-versions.html

90% of all users that connect to the Market are now on Android 2.1 or greater. Android 2.2 and 2.3 haven't brought any kind of huge API changes that require you lock out 2.1 users to get some awesome new feature. The new "big thing" is going to be the Fragments API and it will support all the way back to Android 1.6.

Now, don't get me wrong. I want everyone that can be to be on 2.3 yesterday, but it isn't exactly a big deal.

Apple TV doesn't use a "bad setting" by default. They use whatever you set it to or whatever your DHCP server tells it to use. If you have that set to OpenDNS or Google DNS or whatever you break Akamia. If you have it set to your ISP's DNS which most people will, you have no issue.

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.