decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Learning Android for Java programmers | 214 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Learning Android for Java programmers
Authored by: Anonymous on Monday, May 21 2012 @ 10:41 PM EDT

But I think the key observation that you're missing is that the question is not re: all of Java vs. all of Android. For the purposes of the current trial, the question is limited to the 37 APIs at issue - which (as I understand it) have nothing to do with the differences between the overall Android and Java platforms.

When constrained to writing code that is self-contained, but can call out to the infrastructure defined by these 37 APIs, a Java developer can write 100% valid Android code - and an Android developer can write 100% valid Java code.

Even more - the compiled Java code will be valid input to the bytecode-to- Android step of an Android build, and the first stage compilation that Android source code goes through during an Android build will be valid input to a JVM - it's just Java code, compiled by the Java compiler into regular JVM bytecode.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )