About: Comparison of Java and Android API

Facets (new session)
Description
Metadata
Settings
- Rule:
- Inverse Functional Properties:
- "Same As":

About: Comparison of Java and Android API Goto Sponge NotDistinct Permalink

An Entity of Type : owl:Thing, within Data Space : dbpedia.demo.openlinksw.com associated with source document(s)
QRcode icon

http://dbpedia.demo.openlinksw.com/describe/?url=http%3A%2F%2Fdbpedia.org%2Fresource%2FComparison_of_Java_and_Android_API

This article compares the application programming interfaces (APIs) and virtual machines (VMs) of the programming language Java and operating system Android. While most Android applications are written in Java-like language, there are some differences between the Java API and the Android API, and Android does not run Java bytecode by a traditional Java virtual machine (JVM), but instead by a Dalvik virtual machine in older versions of Android, and an Android Runtime (ART) in newer versions, that compile the same code that Dalvik runs to Executable and Linkable Format (ELF) executables containing machine code.

Attributes	Values
rdfs:label	Comparison of Java and Android API (en) 안드로이드와 자바의 비교 (ko)
rdfs:comment	이 글은 자바와 안드로이드의 API와 가상 머신을 비교하는 글이다. 대부분의 안드로이드 응용 프로그램은 자바로 작성되어 있으나 자바와 안드로이드의 API에는 많은 차이가 있으며, 안드로이드는 자바 가상 머신(이하 JVM)이 아닌 달빅이라는 별개의 가상 머신을 사용한다. (ko) This article compares the application programming interfaces (APIs) and virtual machines (VMs) of the programming language Java and operating system Android. While most Android applications are written in Java-like language, there are some differences between the Java API and the Android API, and Android does not run Java bytecode by a traditional Java virtual machine (JVM), but instead by a Dalvik virtual machine in older versions of Android, and an Android Runtime (ART) in newer versions, that compile the same code that Dalvik runs to Executable and Linkable Format (ELF) executables containing machine code. (en)
dcterms:subject	Android (operating system) Java (programming language) Computing comparisons
Wikipage page ID	32967440 (xsd:integer)
Wikipage revision ID	1121588002 (xsd:integer)
Link from a Wikipage to another Wikipage	Android Runtime Interpreter (computing) JAR (file format) User interface Android (operating system) Java (programming language) Container (abstract data type) Dalvik (software) Android (operating system) Android Honeycomb Apache Harmony Application programming interface Stack machine Pluggable look and feel Swing (Java) Layout manager 32-bit Executable and Linkable Format Graphical user interface Machine code Java (programming language) Java 8 Computing comparisons Abstract Window Toolkit Java bytecode Java virtual machine Register machine Virtual machine Java SE JavaBean Class (file format)
sameAs	Comparison of Java and Android API Comparison of Java and Android API Comparison of Java and Android API
dbp:wikiPageUsesTemplate	dbt:Android dbt:Reflist
has abstract	This article compares the application programming interfaces (APIs) and virtual machines (VMs) of the programming language Java and operating system Android. While most Android applications are written in Java-like language, there are some differences between the Java API and the Android API, and Android does not run Java bytecode by a traditional Java virtual machine (JVM), but instead by a Dalvik virtual machine in older versions of Android, and an Android Runtime (ART) in newer versions, that compile the same code that Dalvik runs to Executable and Linkable Format (ELF) executables containing machine code. Java bytecode in Java Archive (JAR) files is not executed by Android devices. Instead, Java classes are compiled into a proprietary bytecode format and run on Dalvik (or compiled version thereof with newer ART), a specialized virtual machine (VM) designed for Android. Unlike Java VMs, which are stack machines (stack-based architecture), the Dalvik VM is a register machine (register-based architecture). Dalvik has some traits that differentiate it from other standard VMs: * The VM was designed to use less space. * The constant pool has been modified to use only 32-bit indexes to simplify the interpreter. * Standard Java bytecode executes 8-bit stack instructions. Local variables must be copied to or from the operand stack by separate instructions. Dalvik instead uses its own 16-bit instruction set that works directly on local variables. The local variable is commonly picked by a 4-bit virtual register field. Because the bytecode loaded by the Dalvik virtual machine is not Java bytecode and due to the way Dalvik loads classes, it is impossible to load library packages as jar files. A different procedure must be used to load Android libraries, in which the content of the underlying dex file must be copied in the application private internal storage area before it is loaded. (en) 이 글은 자바와 안드로이드의 API와 가상 머신을 비교하는 글이다. 대부분의 안드로이드 응용 프로그램은 자바로 작성되어 있으나 자바와 안드로이드의 API에는 많은 차이가 있으며, 안드로이드는 자바 가상 머신(이하 JVM)이 아닌 달빅이라는 별개의 가상 머신을 사용한다. (ko)
gold:hypernym	Differences
prov:wasDerivedFrom	wikipedia-en:Comparison_of_Java_and_Android_API?oldid=1121588002&ns=0
page length (characters) of wiki page	8729 (xsd:nonNegativeInteger)
foaf:isPrimaryTopicOf	wikipedia-en:Comparison_of_Java_and_Android_API
is Link from a Wikipage to another Wikipage of	Dalvik (software)
is foaf:primaryTopic of	wikipedia-en:Comparison_of_Java_and_Android_API

Faceted Search & Find service v1.17_git139 as of Feb 29 2024

Alternative Linked Data Documents: ODE Content Formats:

RDF

ODATA

Microdata

About

OpenLink Virtuoso version 08.03.3330 as of Mar 19 2024, on Linux (x86_64-generic-linux-glibc212), Single-Server Edition (378 GB total memory, 67 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software