I believe the sentence finishes "how did Google solve this problem"
-
-
He's now explaining how sometimes products are substitutes for each other. Like Coke/Pepsi.
-
yeah, wtf did that have to do with anythinghttps://twitter.com/xor/status/733010718291714049 …
-
I really thought this testimony was going to be about economic effects, not TRANSFORMATIVE FAIR USE
-
Mr. Jaffe, I've been coughing and sneezing a lot. From an economist's perspective, what medicine should I take?https://twitter.com/xor/status/733011272829014016 …
-
Oracle: In your opinion, from an economic perspective, how transformative was Google's use of the 37 APIs in Java and Android?
-
Google objects (finally).
-
Alsup overrules but says jury should remember transformative is not an economic term and that he's speaking to substitution
-
I am dying. I am dead. This is me

-
Mr. Jaffe, from an economist's perspective, was the invasion of Iraq legal under international law?
-
Mr. Jaffe, from an economist's perspective, which pesticide is killing all the bees?
-
Mr. Jaffe, from an economist's perspective, what string do I type into terminal to concatenate these files?
-
Mr. Jaffe, from an economist's perspective, what do the lights at the end of The Great Gatsby signify?
-
Jaffe says that Android harmed Oracle, prevented it from riding that "mobile revolution."https://twitter.com/Ross_Todd/status/733013598465753088 …
-
Presumably through that access to implementations of Java that Google had way before Sun-Oracle did.
-
Mr. Jaffe, please write some Java strings on this easel, in front of the jury. From an economist's perspective, of course.
-
Oracle just literally asked if "from an economist's perspective" whether he thought Google's copying was "fair use."
-
Jaffe concludes based on his analysis, "Google's use was not fair use." From an economist's perspective, of course.
-
What The Fuck
-
No objections from Google.
-
Presumably because they tested the air and found that Alsup wasn't feeling them.
-
But. But. But.
-
Cross-examination of Jaffe now.
-
Google's cross starts with discussing how Keystone "drafted large portions of the report" that Jaffe prepared.
-
Same consulting firm worked with Douglas Schmidt.
-
Google: At the time you formed your opinions, you didn't really know the difference [between declaring code and implementing code], right?
-
-
Going after Jaffe on complexity of Android. Asks whether he has assessed the value of the other parts of Android. He hasn't.
-
Jaffe acknowledges that the code at issue is less than .1% of the total # of lines of code in Android.
-
Google: On your view, predicting the success of platforms is nearly impossible, yes? Jaffe: ...Yes.
- 77 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.