Going over the Rubin email about how "the alternatives all suck" Oracle: AND THEN YOU CAME HERE AND TESTIFIED THE APIS HAD NO VALUE AT ALL
-
-
(These are all mirrors of the Schmidt tests)
-
(Wait for the mic drop I think I know what's coming)
-
He removed declaring code, and then that failed to build.
-
Google: Were you surprised? Astrachan: No. Because when you change the source code, it's common for it to fail to build.
-
Astrachan: I don't think this shows that the 37 packages have any more importance or criticality than any other packages.
-
Not sure I understood correctly — Astrachan did this with non-Java packages?
-
Now we're looking at the visualizations of the API packages provided by Schmidt.
-
Astrachan said that these visualizations are nothing like what Sun and Oracle provided to developers to explain Java.
-
He says there are books and posters showing classes that are distributed by Sun-Oracle for devs.
-
oh man
-
Astrachan is responding to Reinhold it looks like. Oracle objects, says it's not in the scope of what Reinhold said.
-
Reinhold wasn't disclosed as an expert witness, he was brought in as an employee. Oracle withdraws its objection.
-
We're looking at the examples of declaring code, explaining that he can understand what a method does just from the name.
-
He said that during trial, he "suspected" he could guess what the method did, then after trial he went back and looked it up.
-
When he looked it up, his conclusion just based on the name was correct.
-
(So this is about the functionality of the code)
-
Astrachan: ... each part is very descriptive and functional about what the method does.
-
Now addressing Reinhold testimony that declaring code is sometimes more important than implementing code for devs.
-
Astrachan: You can't do that [come to that conclusion].
-
Astrachan: Developers would absolutely care about implementing code.
-
Astrachan: If the declaring code were good, easy to understand, but the implementing code were buggy ... it would be very difficult.
-
Astrachan: Typically, bugs for developers are in their code, not in the library code. .... it would not be so good.
-
I love this.
-
Keep in mind that even if it's obvious for you, it is probably the FIRST TIME anyone has told the jury that bugs in library code are bad
-
Astrachan summary of what Google did with Android: 1) Google selected 37 (not all) packages from Java SE, and used those method declarations
-
2) Wrote implementing code for those declarations 3) Adding other libraries specific to smartphones, like GPS, camera, etc
-
4) Brought in 3rd party libraries for stuff like web browsers and graphics
-
5) Made the Dalvik Virtual Machine 6) Built whole thing on top of Linux.
-
Astrachan: That whole sequence led to this open source, innovative Android platform.
- 35 réponses de plus
Nouvelle conversation -
Le chargement semble prendre du temps.
Twitter est peut-être en surcapacité ou rencontre momentanément un incident. Réessayez ou rendez-vous sur la page Twitter Status pour plus d'informations.