Talk:Dalvik (software)

message: This is a Google employee, can you state that? Sounds like independent.  —Preceding unsigned comment added by 88.251.96.140 (talk) 22:12, 5 December 2008 (UTC)
thread_title: Dan Bornstein

message: I'm a bit confused... Isn't the java bytecode meant to be optimised for weak hardware like mobile devices? I mean, doesn't the necessarity for an "optimiser" that turns java bytecode into something better mean, that the java VMs are really bad? 84.59.120.148 20:24, 13 November 2007 (UTC)
replies: text: Mmyeah, pretty much. --204.99.164.164 (talk) 20:06, 26 February 2008 (UTC)

text: You are right, plus today's ARM processors also embed a JaZelle booster dedicated to directly translate most of the bytecode into native instruction. So Google point about "it's is optimized" is the same as Steve Jobs saying "Java is slow" when you know the iPhone supports Jazelle. Steve is just looking for exclusive application (Java portability would killed its premium) on iPhone, and Google is only looking to workaround Sun royalties. Be sure that if Sun give free royalties to Google for Java usage, then they will directly jump back to real compatible Java using bytecode, retouring the translator as a JIT ;-) TestMan  —Preceding unsigned comment added by 81.57.244.114 (talk) 07:29, 6 April 2009 (UTC)

text: Graphics benchmarks must have their own category; benchmark consumers either care about graphics (games/CAD/image processing), or don't (database/servers/telco/billing systems). Re: Oracle/performance/horrors/"proven by JavaFX", well, that's flame-bait. There will be performance issues with JVM's & graphics for years to come; to be expected w/ layers of abstraction between the hardware & language. (Blame NVidia more than Oracle... plus, this is still Sun's baby, with minimal impact by Oracle one way or the other, which is actually better than expected.)  As an exmaple, just look at the history/performance of Linux/X (see: wayland).  — Preceding unsigned comment added by 148.87.19.206 (talk) 09:07, 4 April 2013 (UTC)
thread_title:  Original Java VM sucks? 

message: Can we have more information on this VM; for example:
* the number and size or registers, 
* whether addresses and data values are distinguished, for example by having dedicated registers for each,
* addressing modes, 
* number of stacks, 
* security checks at runtime, 
* whether or not the VM has, or is intended to have later, a JIT compiler which can compile into native code, 
* whether there is any provision for supporting type-based theorem proving for security assertions, for example to prove whether storage operations can be performed without bounds-checking?
* can it do super-clever things like closures and spaghetti stacks, or is it pretty much a dead-ahead old-fashioned intcode implementation that models a conventional CPU?  
-- The Anome 12:19, 14 November 2007 (UTC)
replies: text: I just added a new Architecture paragraph. There are answers to some of these questions. Hervegirod (talk) 08:56, 8 June 2008 (UTC)

text: I'd like the article to state what this VM is licensed under.  I assume apache.  I ask because this whitepaper:
http://www.spectrumdt.com/documents/SDTAndroidTechnicalWhitePaper_001.pdf
suggested:
"
As such, any phone that would customize the libraries found in
this layer, add libraries or remove them altogether would no longer be able to brand itself as
an Android phone. Furthermore, under this same pledge, its license to the proprietary Dalvik
virtual machine found at the core of the Android platform would be considered null and void.
"
Which I don't believe to be accurate.  Mathiastck (talk) 13:59, 6 April 2009 (UTC)

text: Can anyone clarify what exactly the VM does with the bytecode if it does not JIT-compile it? Does it only interpret and make calls into the kernel or libraries then? 141.117.77.248 (talk) 20:12, 17 April 2009 (UTC)
thread_title:  More information, please? 

message: This page uses copyrighted material from . --204.99.164.164 (talk) 20:04, 26 February 2008 (UTC)
replies: text: Thanks for the hint; I've removed the quotes. Make this article quite broken, though.--Oneiros (talk) 00:46, 23 November 2008 (UTC)
thread_title:  Copyright violation 

message: The last sentence of the second paragraph of the Architecture section is not a sentence. I'm not sure what it's trying to say, but someone should revise it.  —Preceding unsigned comment added by 166.137.8.140 (talk) 19:06, 31 July 2010 (UTC)
thread_title:  Architecture sentence is not a sentence.  

message: It would be good to have some explicit discussion of Dalvik's license in the article. The infobox says it's apache2-licensed. But in the context of the Oracle controversy, there's been discussion about whether the Dalvik VM is in fact open-source at all. Would be grateful for some clarification --mcld (talk) 11:19, 16 August 2010 (UTC)
replies: text: OK, started a section --mcld (talk) 12:03, 16 August 2010 (UTC)
thread_title:  Dalvik's license 

message: This graphic is prejudicial. SCO wanted to charge for linux licenses using what was easily questionable copyright ownership. There is no dispute that Oracle bought Sun in total and thus owns the java copyrights. Thus Oracle should not be framed in the same light as SCO.  —Preceding unsigned comment added by Bilton1 (talk • contribs) 02:11, 27 August 2010 (UTC)
thread_title:  SCOracle graphic 

message: I think this reference is more of a lame attempt at SEO for the Wikipedia entry about that law firm than helpful (or needed) information in the context of Dalvik. Note that the linked Wikipedia entry for said firm has multiple issues, among others: "It is written like an advertisement". Surprise, surprise. I'd suggest removing this reference as long as the many issues of the linked entry aren't solved.
178.83.239.67 (talk) 14:17, 12 October 2010 (UTC)
thread_title:  Reference to Boies, Schiller & Flexner 

message: Does Dalvik make use of the Jazelle instruction set for acceleration (also, is it possible and/or beneficial to do so)? Arny (talk) 10:59, 11 July 2011 (UTC)
replies: text: I did not find any source about that, and also I don't think it's the case, because Jazelle is based on the existing JVM instruction set. Plus Jazelle is closed source technology by ARM, it would seem really strange that Google would have used this technology for their own Virtual machine. Hervegirod (talk) 13:49, 8 May 2012 (UTC)
thread_title:  Jazelle? 

message: Meant to change and wrote summary "Ugly mess of date formats. Only DMY used in main text, however appropriate MDY (WP:STRONGNAT) or YMD used elsewhere." However in second thought DMY might be correct not just because of first use but because of WP:STRONGANT. Dalvik is named after Dalvík in Iceland, a DMY country.. :) Change others? comp.arch (talk) 14:27, 24 March 2014 (UTC)
thread_title:  DMY date format? 

message: Hello fellow Wikipedians,
I have just modified  on Dalvik (software). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20090417091524/http://android.git.kernel.org:80/?p=platform/dalvik.git to http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=NOTICE;hb=HEAD
*Added archive https://web.archive.org/web/20110225035845/http://www.betaversion.org:80/~stefano/linotype/news/110/ to http://www.betaversion.org/~stefano/linotype/news/110/
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—InternetArchiveBot (Report bug) 12:22, 5 December 2016 (UTC)
thread_title:  External links modified