danramos
|
2010-08-17
, 07:41
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#81
|
|
2010-08-17
, 07:43
|
Posts: 3,401 |
Thanked: 1,255 times |
Joined on Nov 2005
@ London, UK
|
#82
|
Taking into account a lot of tools for syntax parsing it is much easy to create a clean Java compiler.
It would be interesting to discover that Google has their own compiler but doesn't distribute it because of copyright/patents/etc.
The Following User Says Thank You to Milhouse For This Useful Post: | ||
|
2010-08-17
, 11:56
|
Posts: 874 |
Thanked: 316 times |
Joined on Jun 2007
@ London UK
|
#83
|
Also, to bolster another point I thought I had right earlier (and apparently did), under the section where it says, "Charles Nutter, explains about what Google did and why he thinks it did it and what might result:"
|
2010-08-17
, 15:15
|
Posts: 992 |
Thanked: 738 times |
Joined on Jun 2010
@ Low Earth Orbit
|
#84
|
|
2010-08-17
, 19:30
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#85
|
I very much doubt Google will base their defence on the "wrongness of software patents", so why the hell should supporters of no software patents care whether Google wins or not?
I think is the complete Charles Nutter piece
http://blog.headius.com/2010/08/my-t...-v-google.html
It is a long read but a great one.
|
2010-08-17
, 19:34
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#86
|
Nobody is talking about bytecode conversion at run-time - the conversion happens when the applications are compiled.
I really doubt that - creating a Java compatible language compiler that keeps pace with each new version of Java would be a serious undertaking and one that is completely unnecessary when you can just convert the bytecode.
And since being able to convert the bytecode is a necessary
requirement in order to assist with the porting of native Java classes to Dalvik it makes no sense to go down the language compiler route when instead you can just convert the bytecode at the end of the compilation process. There really is no need to re-invent the wheel.
Seemingly anyone who creates an app for Android that runs in the Dalvik VM would end up using the dx tool during the creating of their application. This would mean Google, device manufacturers, third-party developers all use the dx tool.
If that were true it would open Google up to all sorts of accusations from their partners since the playing field would no longer be level. All Android developers should have access to the same SDK and development tools, I'm sure the partners would be pretty hacked off to discover that Google were building their apps with other (better?) tools that were denied to them.
The Following User Says Thank You to egoshin For This Useful Post: | ||
|
2010-09-16
, 21:50
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#87
|
The Following User Says Thank You to danramos For This Useful Post: | ||
|
2010-09-16
, 22:11
|
Posts: 2,829 |
Thanked: 1,459 times |
Joined on Dec 2009
@ Finland
|
#88
|
I had to come back to share this EXCELLENT article published on Groklaw today that summarizes Dalvik with specific detail with an eye toward understanding it well enough to follow the Oracle USA case against Google:
What is Dalvik? by Mark Murphy
http://www.groklaw.net/article.php?s...00915143729255
The Following User Says Thank You to slender For This Useful Post: | ||
|
2010-09-16
, 22:19
|
|
Posts: 220 |
Thanked: 49 times |
Joined on Aug 2010
@ england
|
#89
|
thanks for the link. Article started nicley but where are the rest of it? Guy just did introduction and did not give any answers to questions what were first put on table. Or actually he answered only to one question.
|
2010-09-16
, 22:29
|
|
Posts: 741 |
Thanked: 900 times |
Joined on Nov 2007
@ Auckland NZ
|
#90
|
Tags |
bride-of-darl, chicks roosting, scoracle |
|