This comment got me thinking, "What have Oracle really shown about the
organization of the API(s)?"
This is what I have found after a quick
look:
Day 5:
Oracle: Android ships with implementations of
all of these classes using these same names, the same as the Java API?
Dan
Morrill: Yes.
Oracle: Not only does the Android API use the same names, it
also uses the same form and organization as Java?
Dan Morrill:
Yes.
Day 4 Bloch cross-exam (google)
Q. In the Java language, what
determines the implementation/organization of a library?
A. Fully qualified
names: e.g, java.lang.math.cosine(), where java.lang is the package, math is the
class, and cosine in the method (goes into detail about the periods and the
upper/lower case conventions for names).
...
Q. Prior to this trial, had
you ever heard the phrase "Structure, organization, and sequence" in reference
to APIs?
A. No.
day 3.
Oracle: Exhibit 610 [again, Oracle
mucks up their extibits. 610.2 get shown.]
Mark Reinhold: [From the point of
view of the computer], very little API organization is required by the VM. We
could have given them completely random names and put them into one huge
package. The design goal was that API's should be easy to learn and easy to use.
Other considerations:
1) performance is important
2) Portability is important
[wouldn't want to define an API that is specific to Windows].
Unless
I'm missing some major argument, they don't seem to have said much about
organization or why it would be important.
[ Reply to This | Parent | # ]
| 
