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
THIS!!! | 451 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
THIS!!!
Authored by: lwoggardner on Friday, May 04 2012 @ 12:44 AM EDT
absolutely is the crux of it, and google raised in evidence.

Compatibility of other people's programs, libraries and frameworks which are stacked on top of each other in what is called "dependency ****" in the trade.

At the root of all those dependances is the java standard libraries, aka the 37 packages at issue here. If you don't have an implementation of those apis then none of those libraries could be reused on Android.

**** a non Groklaw suitable term.

[ Reply to This | Parent | # ]

Software Quality
Authored by: WWWombat on Friday, May 04 2012 @ 08:05 AM EDT
15 years ago, our company (at the time) went through a few iterations of attempting to improve the quality of the software we wrote. One direction we tested was Java - a language that I stuck with, even if the company didn't.

At the time, there was little of the "test-led" development concept, but Java itself was a massive improvement on previous languages, in that it gave you so much checking at compile-time.

Since then the numerous 3rd-party libraries, such as Joda and Junit, and the development tools (such as Eclipse) have all helped to improve the ease of software development *and* improve the quality.

That is 15 years where state-of-the-art has leveraged off the top of the Java APIs. The point, therefore, that there is so much 3rd party stuff that *also* depends on the Java APIs, but independently adds to the Java world, is hugely important to compatibility. Thank you for mentioning it!

Of course, when Java was in its infancy, it was leveraging off the top of C and C++ in the same way.

[ 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 )