| 1. | | Our unrealistic views of death, through a doctor’s eyes (washingtonpost.com) |
| 349 points by llambda on Feb 19, 2012 | 254 comments |
|
| 2. | | How Forbes Stole a New York Times Article and Got All The Traffic (nickoneill.com) |
| 247 points by cnolden on Feb 19, 2012 | 60 comments |
|
| 3. | | How key-based cache expiration works (37signals.com) |
| 212 points by Thibaut on Feb 19, 2012 | 35 comments |
|
| 4. | | Hackathons are nonsense (scripting.com) |
| 185 points by PixelRobot on Feb 19, 2012 | 71 comments |
|
| 5. | | The Great Web Framework Shootout – On GitHub (github.com/seedifferently) |
| 167 points by stesch on Feb 19, 2012 | 72 comments |
|
| 6. | | How to Make and Use a Transparency Grenade (transparencygrenade.com) |
| 157 points by tokenadult on Feb 19, 2012 | 38 comments |
|
| 7. | | Parsing Techniques - A Practical Guide (dickgrune.com) |
| 158 points by llambda on Feb 19, 2012 | 20 comments |
|
| 8. | | Berkeley Computer Vision Class (vision-class.org) |
| 136 points by myffical on Feb 19, 2012 | 16 comments |
|
| 9. | | The town is no longer friendly for business (swombat.com) |
| 135 points by mikeleeorg on Feb 19, 2012 | 108 comments |
|
| 10. | | Alan Turing's 1950s tiger stripe theory proved (physorg.com) |
| 132 points by acangiano on Feb 19, 2012 | 15 comments |
|
| 11. | | Oracle v. Google: "the value of this case keeps getting smaller and smaller" (groklaw.net) |
| 133 points by grellas on Feb 19, 2012 | 23 comments |
|
| 12. | | The Forgetting Pill Erases Painful Memories Forever (wired.com) |
| 131 points by pier0 on Feb 19, 2012 | 48 comments |
|
| 13. | | Spicing unix shell scripts (cyberciti.biz) |
| 123 points by pareshverma91 on Feb 19, 2012 | 14 comments |
|
| 14. | | Hacker News clone for Python (pythonmeme.com) |
| 108 points by arowser on Feb 19, 2012 | 30 comments |
|
| 15. | | Objective-C literals for NSDictionary, NSArray, and NSNumber (cocoaheads.tumblr.com) |
| 102 points by julien_p on Feb 19, 2012 | 57 comments |
|
| 16. | | How casinos distract (ketyov.com) |
| 100 points by tortilla on Feb 19, 2012 | 36 comments |
|
| 17. | | Show HN: A distributed Recommendation Engine based on Redis + Ruby (and C) (github.com/paulasmuth) |
| 97 points by paulasmuth on Feb 19, 2012 | 11 comments |
|
| 18. | | It's easier to ask for forgiveness than it is to get permission (bemmu.posterous.com) |
| 94 points by bemmu on Feb 19, 2012 | 51 comments |
|
| |
|
|
| 20. | | Show HN: StyleBootstrap, create unique Bootstrap design live (stylebootstrap.info) |
| 88 points by creatom on Feb 19, 2012 | 7 comments |
|
| 21. | | Physicists Create a Working Transistor From a Single Atom (nytimes.com) |
| 81 points by dazbradbury on Feb 19, 2012 | 14 comments |
|
| 22. | | High-wage skills, or why you might want to learn Clojure if you're not a lawyer (onlinelabor.blogspot.com) |
| 82 points by Panos on Feb 19, 2012 | 62 comments |
|
| 23. | | You Are Not Ruthless Enough (playswithfire.com) |
| 79 points by wallflower on Feb 19, 2012 | 19 comments |
|
| 24. | | Facebook is losing E-Commerce (nikcub.appspot.com) |
| 78 points by nikcub on Feb 19, 2012 | 32 comments |
|
| 25. | | Show HN: devsigh.com - post all your stories of developer sigh (devsigh.com) |
| 73 points by chargrilled on Feb 19, 2012 | 33 comments |
|
| 26. | | Save the Libraries. Cut University Funding Instead. (jbgst.tumblr.com) |
| 70 points by johnnybgoode on Feb 19, 2012 | 61 comments |
|
| 27. | | My dual core can beat up your quad core, and other mobile CPU mysteries (icrontic.com) |
| 64 points by primesuspect on Feb 19, 2012 | 12 comments |
|
| 28. | | Luerl - Lua on the Erlang VM (erlang.org) |
| 61 points by EvanMiller on Feb 19, 2012 | 8 comments |
|
| 29. | | Exploit to detect which Social Networks you are logged into (tomanthony.co.uk) |
| 57 points by TomAnthony on Feb 19, 2012 | 11 comments |
|
| 30. | | The minimal code required in a HTML5 page (chetankjain.net) |
| 57 points by cjain on Feb 19, 2012 | 17 comments |
|
|
| More |
I can still vividly remember how, as a young lawyer, I was so stunned by the sheer phoniness of this so-called expert report - here were a bunch of bungling, bureaucratic committee types who couldn'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. Everything 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 "had transpired" with this or that result "having ensued." 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: "this is the suit-and-tie version of a stick-up in some back alley." And the case worked out true to form, with what must have appeared to be surreal results from the viewpoint of the midwest firm'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 "digest sheet," 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 "delay damages report," 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.
As the facts are emerging in Oracle'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, when it is all put in context, 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's lawyers have put together to decimate the report of Oracle's key damages expert. All I could think of as I read this was how this sort of phony "expert analysis" 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.
Oracle will of course fight to resist Google'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's report (see http://news.ycombinator.com/item?id=3500459 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.