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 : el.dbpedia.org associated with source document(s)

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)
rdfs:comment	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)
dbp:wikiPageUsesTemplate	dbt:Android dbt:Reflist
Subject	Android (operating system) Java (programming language) Computing comparisons
gold:hypernym	Differences
prov:wasDerivedFrom	http://en.wikipedia.org/wiki/Comparison_of_Java_and_Android_API?oldid=1003608602&ns=0
Wikipage page ID	32967440 (xsd:integer)
page length (characters) of wiki page	8709 (xsd:nonNegativeInteger)
Wikipage revision ID	1003608602 (xsd:integer)
Link from a Wikipage to another Wikipage	Machine code 32-bit computing API Abstract Window Toolkit Android (operating system) Android Honeycomb Android Runtime Apache Harmony Android (operating system) Java (programming language) JavaBeans Java (programming language) Java Platform, Standard Edition Java bytecode Java class file Java version history Java virtual machine Dalvik (software) Pluggable look and feel Container (abstract data type) Virtual machine Computer graphics Swing (Java) Executable and Linkable Format Interpreter (computing) User interface Stack machine JAR (file format) Layout manager Register machine Computing comparisons
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)
foaf:isPrimaryTopicOf	http://en.wikipedia.org/wiki/Comparison_of_Java_and_Android_API
is Link from a Wikipage to another Wikipage of	Dalvik (software)
is foaf:primaryTopic of	http://en.wikipedia.org/wiki/Comparison_of_Java_and_Android_API

Faceted Search & Find service v1.17_git151 as of Feb 20 2025

Alternative Linked Data Documents: ODE Content Formats:

RDF

ODATA

Microdata

About

OpenLink Virtuoso version 07.20.3240 as of Nov 11 2024, on Linux (x86_64-ubuntu_focal-linux-gnu), Single-Server Edition (72 GB total memory, 1 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2025 OpenLink Software