"Google Wrote 23% of Android Donut"
-
-
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?
-
Part of being involved with consulting firm called Keystone.
-
Had help from 4 different people, including someone who did work for another expert on this case.
-
Back to this thing that Google is doing:https://twitter.com/sarahjeong/status/732630010293444608 …
-
mannn
-
It's stipulated in this case that Java-the-language is free and open to use
-
Apparently in a deposition DS said it wasn't
-
DS: I did not understand what "free and open" meant at the time, I have since learned. UHHHHHHHHHHHHHHHHHHHH
-
?????????????
-
Google continuing with cross and he's actually holding up pretty well but that one part does not seem adequately explained
-
Google clarifying that these visualizations he testified as to are created by someone else.
-
Google: You don't even own a copy of the software, do you? DS: ... it's a tool accessed through the browser. ¯\_(ツ)_/¯
- 25 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.