Still some deep frowning over in the jury box.
-
-
Oh this one is a cute slide
-
"Google Wrote 23% of Android Donut"
-
Testifies that bulk is 3rd Party, 13% unspecified, and 23% from Google.
-
Google/Oracle now disputing on whether it's proper to let this testimony. Alsup says "Google is correct" but lets Oracle go
-
And says Astrachan respond to it later.
-
Says the breakdown of Google's code is 14% code, 9% blank lines and comments
-
Now a comparison side of a cluster map of Java SE 5 and a cluster map of Android Gingerbread.
-
I just sneezed in court. Praying that Alsup doesn't kick me out with a packet of tissues.
-
On java.security: DS: ... we all know security is good, so... that would be an important thing to have.
-
Now showing that Sun's SavaJe OS and Android OS have a similar architecture.
-
Says that the "layers" of the SavaJe OS were equivalent to the "layers" in Android.
-
Hmmmm
-
for example, "both of them have virtual machines, both of them run on top of operating system kernels"
-
-
DS: Full-stack operating systems were being used prior to the release of the Android mobile device.
-
Testifying that "Android technology has Java-based predecessors" with a comparison of the T-Mobile Sidekick
-
It's 12:35. It feels like I've been here for an eternity.
-
DS testifies that "design of Java APIs is unique and creative," by showing that there are 4 different ways to set up collections libraries
-
Now talking about JGL, pronounced "juggle."
-
the gathering of the JGLos
-
i'm tired of this, make him whiteboard code
-
Says there's nothing about the code, nothing about convention & custom, that made the designers design the libraries in the way they did
-
—it was a creative decision.
-
Three concluding points for DS:
-
* Google's copying did not alter the declaring code and design of the 37 Java APIs
-
* The copied declaring code and design are creative
-
* The copied API packages are substantial
-
Direct over. Cross-exam begins.
-
Google: You first became involved in this litigation in November 2015, correct?
- 37 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.