Linked by Thom Holwerda on Thu 28th Oct 2010 20:07 UTC, submitted by poundsmack
Permalink for comment 447608
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2010-03-30
... a good thing for Google to do would be to drop Java, creating a (slightly) different language that still targets their JVM? That would be an opportunity for a simpler syntax. Oracle can't sue over code resemblance... or can they? Just see how much Java looks like C++.
Google would create a converter, that would take Java code, output Google's X language code. C++ to Java and Java to C++ converters exist. So that shouldn't pose any problems either.
They would provide said language X in the SDK IDE if there's an IDE in the SDK and ask developers to switch languages and it'll all be done. If Apple could convert devs to Objective-C, Google too can succeed in doing that.
Not saying the lawsuit would suddenly stop but it's a way out of this morass that Google should have not put themselves in by creating a different VM, especially with openJDK available.
In the end, I'm just wondering why and how Google felt the need for Dalvik... weren't they calling for trouble?