Quote:
Originally Posted by MicroNix 
Just had to comment on the end of the article regarding the iPhone clone garbage. Take a good look at the Google phones and you'll see they don't *look* anything like the iPhone. The iPhone is just a application launcher on its primary screens; boring and bland. Google Android makes the iPhone look like the iPhone is to the Palm Treo; yesterday's technology. There's no comparison!

Just had to comment on the end of the article regarding the iPhone clone garbage. Take a good look at the Google phones and you'll see they don't *look* anything like the iPhone. The iPhone is just a application launcher on its primary screens; boring and bland. Google Android makes the iPhone look like the iPhone is to the Palm Treo; yesterday's technology. There's no comparison!
If that were actually the case, why isn't the iPhone being compared to these 'trend setting, envelope pushing' Android phones, instead of being the other way around? Even among very Android-friendly CNET reviews, the best you can hear about Android models is wording along the lines of "this is likely the best attempt yet to take on the iPhone."
Android may offer you or other tech-savvy people the ability to do things not offered on the iPhone (and that's a short list!) but it's not broadly appealing to users (too complicated, missing major features, stuff simply doesn't work - try connecting to inflight WiFi), carriers are not as interested in Android as they once were, and hardware makers see Android as being a common denominator that will reduce their offerings into commodity products just like Windows took away most of the value of PCs.
Only the two biggest losers have focused on Android (Motorola and Sony Ericsson, the only two major smartphone makers unable to make money in recent years), while HTC & LG have hedged their bet with WiMo/WP7, Samsung has its own Bada backup plan, and Nokia, HP, RIM are all hanging on to their own platforms. Do you know something they all don't?
Quote:
And to the article itself, a developer that already pulled all this apart finds virtually none of the accused code is actually found in the end shipping product. Sorry for the waste of bytes on this article...
Actually that didn't happen. Instead, a guy made some excuses for the files in question for ZDNet, and Ars similarly suggested that the new files found "were not a smoking gun," while also admitting that is was still a big problem for Google.
A confident rebuttal isn't necessarily "the last word" on a subject just because it might be what you want to hear.
The real issue for Google isn't these newly reported files anyway - they're just additional evidence that Google isn't doing a great job in managing Android.
The REAL problem, the one Oracle is suing over, is a series of files that you get when you disassemble Java, which turns out to be exactly what you get when you look at Android. Early development simply churned out Java and called it Android, then fixed some mobile-related problems with Java, such as its VM design, and called it non-Java and therefore not needing to license Java IP.
The problem is, there's lots of evidence that Android simply is Java, and these additional files just indicate how sloppy Android development is. Taking GPL code and replacing the license text with a more permissive license that allows commercial, proprietary development isn't just illegal and an affront to IP laws, it's also a slap in the face to the very Free and Open Source ideals Android is supposedly promoting, and very obviously a sign that Android developers don't respect others' IP.
Oracle/Sun offered some portions of Java under GPL for specific reasons. Google essentially took Oracle/Sun's GPL code and used it opposite of what it was licensed to do. Google had no right to do that, and appears to have assumed not just damages (which are pretty obvious given the hammering that Android has done to JavaME as a mobile platform) but also surrounded the event with lots of evidence that backs up that this was not just an isolated incident or automated mistake, but simply how Google rolls.
Every major cash-cow Google product is stolen IP: it stole its key paid search placement IP from Overture, it stole Android from Sun's Java, and WebM is pretty clearly an infringing implementation of MPEG, just like virtually every other proprietary codec On2 created. At least Microsoft wrote some of its own apps.
Google is killing off competition in the marketplace by simply stealing other people's IP and "selling" it as its own ad platform. Ask Gizmodo how the whole "selling of stolen goods" worked out.
But really, the Oracle case against Google is more than even that: Oracle is asserting a series of patent claims against Google's modified Java VM that it calls Dvalik. When Google first announced that it was doing this in 2007, the tech world gasped, but Sun never took any action so everyone seemed to decide it was okay. Well now Oracle is saying, hell no, you got to pay.
The Oracle case against Google is a lot like the Apple/Pystar case, except that Google simply changed more of the code it took, like Pystar, to sell its own product with less work.
Google still overtly repurposed Java to "create" Android. It could have gotten away with this if it had worked harder to do it the right way, making a very clean effort not to contaminate Android with obvious code theft from Java. It simply didn't, as is obvious in a number of parallel cases of evidence, not just the new files in question.









) and all things idiot idiotphone, idiotmac, idiotpod, idiotpad,