That's not necessarily true. In Texas if there's no posted speed limit, then the speed limit is 30MPH.

Ignorance of the law...

You're right. Everything on the phone is an app including the phone (which *shouldn't* use data).

Phone, contacts, the "killswitch", GPS if you allow cell tower helpers, etc..

Had the testers actually turned off data services rather than shut down some apps, we'd have a better picture of what was really going on. As simple a test as that would be, I'm led to believe they chose a different route on purpose.

Spot on with your WP7 comparison too.

Maybe BS as to who the lawsuit is targeting? Nobody in the article seems to suggest that Apple may be at fault here. The testing method is certainly weak, and if the phone is actually causing the issue, it wouldn't be AT&T's responsibility to warn the user, it would be Apple's.

Void your warranty with a soldering iron.

They were examples of things Microsoft did that surpassed Apple. Handhelds weren't very niche in the enterprise... the Fortune 500 companies I worked for had tons of iPaq's. And Windows Mobile was never abandoned, they just lost marketshare when they rested on their laurels.

DOS != Windows. Same as the OS on Apple ][s != Mac OS and OSX.

Admittedly Microsoft was in front of Apple on servers, but we all know how that went for Apple.

My Galaxy S came with 512MB of flash, 16GB of internal SD (which apps can be installed to, and internal SD is flash as well) and an external MicroSD slot capable of 32GB. And the Super AMOLED screen is not as bright as the retina display, but handles color much better (including a true black). Granted not many Android devices have Super AMOLED, but the choice is there. The iPhone 4 also has slightly better resolution. The Galaxy-S has slightly better camera resolution.

The US with contract prices are very similar. The out of contract prices are a bit different though. Currently the iPhone 4 16GB with no contract is $600 and the Captivate (AT&T Galaxy S) is $500. Similar prices to probably most folks, but $100 is $100.

And that's with the possibility of the Captivate having a total of 48.GB of storage. Add $25 to the iPhone price and you can get their largest at 32GB. The difference in storage is Apple allows for use of all of the internal storage for apps, data, etc.. while pre 2.2 Androids do not. They do now, of course.

The Cricket (and comperable companies) plans are interesting. If coverage is widespread, I would think more and more people would be shifting over. I'd also think people would be more into the idea of buying outright like the rest of the world does. It's what I did though I still use AT&T because of coverage where I live and work.

Too true, and my personal boycott has been going on for ~5 years now. Of course, I'm not a kid and shiny doesn't distract me in the same way.

I don't miss blue ray (I'm with you on the spelling), and don't have any Sony products in my house. Strangely enough, I'm still able to watch tv/movies, listen to music, and use the intertubes with relative ease.

And my Fender Bassman amp. Good tubes are getting harder to find though, expecially the matched pairs from radios used in WWII.

Mod +1 insightful... you saw through his marketingspeak iOS on the whole. Now that Google TV and Android based media players are beginning to ship, it will only chip away further at iOS on the whole.

But yeah, in the smartphone world, Android has iOS in the rear view mirror. Just like Apple had RIM, and RIM had Palm, and Palm had Microsoft....

LIkewise you cannot say Android phones and iPhones are similarly priced. There are a handful of iPhone versions, and dozens of Androids. Which comparison would you like to draw? iPhone vs. similar hardware Android? Top of the line iPhone vs. top of the line Android? Entry level iPhone vs. entry level Android?

Comparisons always have a fail point of some magnitude.

Of note, my Galaxy S was cheaper than my iPhone 4, and I bought both outright in the US.

Consider the apps in Marketplace and the App Store. Marketplace has surpassed 200,000 apps, App Store has surpassed 300,000. How many duplicates are there in each store? How many different fart or gun sound apps do you actually need?

Pound for pound, the same apps exist in both stores. It's the duplication at this point that keeps them seperate. Choice is good, but there comes a point when oversaturation just confuses users. Which mail app do I like this week? How many background changers is too many?

And I think you're thinking a bit backwards on making a living selling apps. If the App Store has more apps, and Android is outselling iOS, it should be easier to make money selling Android apps. I can attest to that personally.

I'm pretty tired of the uninformed that talk about having to get Android apps running on hundreds of devices. All you have to do is design your screens to be dynamic and gracefully bow out of functionality the device may not support. It's the same as writing halfway decent code for the browser. Do you always know what resolution the user will have set or whether or not their browser is maximized? What do you do when they hit print but do not have a printer set up?

I've already begun to give up on iOS. Way too locked down, their app approval process is frustrating at best (and special approval for background services since the devices really don't multitask), no sideloading (unless it's jailbroken), Objective C sucks... it's just not worth the hassle. If I can get Appcelerator or Phonegap working fine I MAY stick with iOS apps but it's not likely otherwise.

DOS, Windows, Servers, Handhelds (iPaq)... there's a much longer list than 1 ;)

I develop for Android, iPhone and Blackberry (sorry Nokia, you have too small a user base in the US). I really like the APIs in Android actually.

I think you're way off on performance, and have no idea where your "almost any Android implementation" thoughts come from. I just don't see the issues you do.

I think the problem is that the new system should account for this as well. Unless /. wants to run the perpetual beta tag on it like Google.

Replacement systems should always consider the functionality in the previous systems that the users liked. Looks like they missed one here.

So what that means for me is abandoning the new system and continuing to use the old unless/until they address this. And that makes the effort in creating the new system wasted to me.