<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>esja</author><text>Thanks so much for the time you put into your posts. They always teach me something.&lt;p&gt;The overall theme brought this to mind:&lt;p&gt;&quot;If you give me six lines &amp;#60;of code&amp;#62; written by the hand of the most honest of men, I will find something in them which will hang him.&quot; -- Cardinal Richelieu</text><parent_chain><item><author>grellas</author><text>I began my legal career working for several years at in Big Law. In one case, a stultifying bureaucratic management for a major steel company was building a new plant. After hiring a firm out of the midwest to manage the construction on a fixed-fee contract, it proceeded to make life miserable for that firm by making never-ending revisions to the project plans throughout the course of construction and this not only caused that firm to incur cost overruns but also had the effect of causing substantial delays in getting the work done. Everything was done through a multi-layered committee committee structure, with memos continually being circulated about needs to separate the &quot;wheat from the shaft&quot; and like gems. When it was all done, this mega-sized steel company went out and hired a professional hatchet firm to assemble a &quot;delay damages report&quot; (I don&apos;t remember the exact name but I am sure it was much more high-toned than my description here). It then used this report to send a demand letter to the midwest firm, claiming that their management of the construction project was inept and that it had to pay millions of dollars in damages on account of the delays in construction. When they refused, they got sued for the claimed damages.&lt;p&gt;I can still vividly remember how, as a young lawyer, I was so stunned by the sheer &lt;i&gt;phoniness&lt;/i&gt; of this so-called expert report - here were a bunch of bungling, bureaucratic committee types who couldn&apos;t make a key decision to save their lives using a sham report to try to lay the blame for their own faults at the feet of an innocent firm that had simply done its job. &lt;i&gt;Everything&lt;/i&gt; in that report was couched in passive voice and dressed in self-important language - to a point where you had no idea who had done what but had only a vague sense that this or that &quot;had transpired&quot; with this or that result &quot;having ensued.&quot; What is worse, the report was replete with dishonest (and obviously deliberate) renderings of key facts and with conclusions that could only be reached by the most absurd disregard of logic imaginable. I remember thinking to myself: &quot;this is the suit-and-tie version of a stick-up in some back alley.&quot; And the case worked out true to form, with what must have appeared to be surreal results from the viewpoint of the midwest firm&apos;s executive management. Six lawyers and four paralegals were assigned to the case. Thousands of boxes of documents were assembled with lawyers and paralegals being tasked to go through each document mindlessly summarizing it on a &quot;digest sheet,&quot; with the results ultimately to be compiled into an omnibus analysis report that could in turn be used by competing experts to attempt to rebut the absurdities of the original report. Thousands of hours of billable time racked up and this process was maybe 10 or 15% done when I decided to do a very careful analysis of a relatively few key documents only, to put the story in a context that readily demonstrated the sham nature of the &quot;delay damages report,&quot; to summarize everything in a 50-page write-up, and to give that to the partner in charge. Within a short time, the executive management of our client used that write-up to meet face-to-face with their counterpart executives on the other side and the case quickly settled for a very modest money payment. What a mess, I thought at the time, and all from a phony expert report.&lt;p&gt;As the facts are emerging in Oracle&apos;s attack upon Google, it is clear that there are many complex elements here by which Android might ultimately be found to infringe upon Java in this or that respect but it is equally clear that, &lt;i&gt;when it is all put in context&lt;/i&gt;, the damage claims being asserted by Oracle are about as phony as one could imagine. This Groklaw piece does a splendid job of picking the high points from the critique that Google&apos;s lawyers have put together to decimate the report of Oracle&apos;s key damages expert. All I could think of as I read this was how this sort of phony &quot;expert analysis&quot; remains as prevalent as it did back in my early days of lawyering (over 30 years ago) - different legal context, different facts, same exact techniques, same sort of hired guns. It is enough to give anyone a very jaded view of law and how its outworkings can harm people. Here, Google is more than capable of being able to afford to hire the best in order to defend itself. But what does an average person or company do when faced with such situations? It is truly dismaying to contemplate.&lt;p&gt;Oracle will of course fight to resist Google&apos;s challenges to its damages claims and it will be up to the judge to decide. But the judge recently warned Oracle that this cycle will likely be its last chance to fix the problems with its expert&apos;s report (see &lt;a href=&quot;http://news.ycombinator.com/item?id=3500459&quot; rel=&quot;nofollow&quot;&gt;http://news.ycombinator.com/item?id=3500459&lt;/a&gt; for a detailed analysis of this) and so this will soon reach a decisive point. The result will be, I believe, that Oracle will get its day in court but will only be able to proceed with a much-stripped-down version of its claims - something that might hurt Google a bit financially but will pose no real threat to the Android platform as a whole and will amount in time to nothing more than a blip on the radar.</text></item></parent_chain></comment><story><title>Oracle v. Google: &quot;the value of this case keeps getting smaller and smaller&quot;</title><url>http://www.groklaw.net/article.php?story=20120218041255197</url><text></text></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>meow</author><text>Once this case ends - one way or the other - will Oracle be able to sue Google again by picking up some more patents (from its 500 odd java patents) ? Or is this case the end of suing based on Java related patents...</text><parent_chain><item><author>grellas</author><text>I began my legal career working for several years at in Big Law. In one case, a stultifying bureaucratic management for a major steel company was building a new plant. After hiring a firm out of the midwest to manage the construction on a fixed-fee contract, it proceeded to make life miserable for that firm by making never-ending revisions to the project plans throughout the course of construction and this not only caused that firm to incur cost overruns but also had the effect of causing substantial delays in getting the work done. Everything was done through a multi-layered committee committee structure, with memos continually being circulated about needs to separate the &quot;wheat from the shaft&quot; and like gems. When it was all done, this mega-sized steel company went out and hired a professional hatchet firm to assemble a &quot;delay damages report&quot; (I don&apos;t remember the exact name but I am sure it was much more high-toned than my description here). It then used this report to send a demand letter to the midwest firm, claiming that their management of the construction project was inept and that it had to pay millions of dollars in damages on account of the delays in construction. When they refused, they got sued for the claimed damages.&lt;p&gt;I can still vividly remember how, as a young lawyer, I was so stunned by the sheer &lt;i&gt;phoniness&lt;/i&gt; of this so-called expert report - here were a bunch of bungling, bureaucratic committee types who couldn&apos;t make a key decision to save their lives using a sham report to try to lay the blame for their own faults at the feet of an innocent firm that had simply done its job. &lt;i&gt;Everything&lt;/i&gt; in that report was couched in passive voice and dressed in self-important language - to a point where you had no idea who had done what but had only a vague sense that this or that &quot;had transpired&quot; with this or that result &quot;having ensued.&quot; What is worse, the report was replete with dishonest (and obviously deliberate) renderings of key facts and with conclusions that could only be reached by the most absurd disregard of logic imaginable. I remember thinking to myself: &quot;this is the suit-and-tie version of a stick-up in some back alley.&quot; And the case worked out true to form, with what must have appeared to be surreal results from the viewpoint of the midwest firm&apos;s executive management. Six lawyers and four paralegals were assigned to the case. Thousands of boxes of documents were assembled with lawyers and paralegals being tasked to go through each document mindlessly summarizing it on a &quot;digest sheet,&quot; with the results ultimately to be compiled into an omnibus analysis report that could in turn be used by competing experts to attempt to rebut the absurdities of the original report. Thousands of hours of billable time racked up and this process was maybe 10 or 15% done when I decided to do a very careful analysis of a relatively few key documents only, to put the story in a context that readily demonstrated the sham nature of the &quot;delay damages report,&quot; to summarize everything in a 50-page write-up, and to give that to the partner in charge. Within a short time, the executive management of our client used that write-up to meet face-to-face with their counterpart executives on the other side and the case quickly settled for a very modest money payment. What a mess, I thought at the time, and all from a phony expert report.&lt;p&gt;As the facts are emerging in Oracle&apos;s attack upon Google, it is clear that there are many complex elements here by which Android might ultimately be found to infringe upon Java in this or that respect but it is equally clear that, &lt;i&gt;when it is all put in context&lt;/i&gt;, the damage claims being asserted by Oracle are about as phony as one could imagine. This Groklaw piece does a splendid job of picking the high points from the critique that Google&apos;s lawyers have put together to decimate the report of Oracle&apos;s key damages expert. All I could think of as I read this was how this sort of phony &quot;expert analysis&quot; remains as prevalent as it did back in my early days of lawyering (over 30 years ago) - different legal context, different facts, same exact techniques, same sort of hired guns. It is enough to give anyone a very jaded view of law and how its outworkings can harm people. Here, Google is more than capable of being able to afford to hire the best in order to defend itself. But what does an average person or company do when faced with such situations? It is truly dismaying to contemplate.&lt;p&gt;Oracle will of course fight to resist Google&apos;s challenges to its damages claims and it will be up to the judge to decide. But the judge recently warned Oracle that this cycle will likely be its last chance to fix the problems with its expert&apos;s report (see &lt;a href=&quot;http://news.ycombinator.com/item?id=3500459&quot; rel=&quot;nofollow&quot;&gt;http://news.ycombinator.com/item?id=3500459&lt;/a&gt; for a detailed analysis of this) and so this will soon reach a decisive point. The result will be, I believe, that Oracle will get its day in court but will only be able to proceed with a much-stripped-down version of its claims - something that might hurt Google a bit financially but will pose no real threat to the Android platform as a whole and will amount in time to nothing more than a blip on the radar.</text></item></parent_chain></comment><story><title>Oracle v. Google: &quot;the value of this case keeps getting smaller and smaller&quot;</title><url>http://www.groklaw.net/article.php?story=20120218041255197</url><text></text></story>