A user writes "Anyone familiar with the piracy debate knows about the claims from organizations like the RIAA that piracy causes billions of dollars in damages and costs thousands of jobs. Other studies have concluded differently, ranging from finding practically no damages to a newer study that cites 'up to 20%' as a more accurate number (PDF). I figure there's got to be an easier way to do this, so here's my question: Does anyone know of any creative works that were provably a financial failure due to piracy? The emphasis on 'provably' is important, as some form of evidence is necessary. Accurately and precisely quantifying damages from p2p is impossibly hard, of course, but answering questions like this may lead us to a clearer picture of just how harmful file sharing really is. I would think that if piracy does cause some amount of substantial harm, we would see that fact reflected in our creative works, but I've never heard of a work that tanked because people shared it online."

History's Coming To writes "Several writers for the ScienceBlogs.com collective have publicly resigned from the site, and many more have voiced concerns over parent company Seed's decision to include a paid blog under the nutrition category from PepsiCo. The blog was to be written by PepsiCo food scientists, detailing their work. The UK's Guardian newspaper has picked up on the story, and includes a letter from Seed editor Adam Bly which covers the company's rationale." The ScienceBlogs Team later canceled the PepsiCo blog and apologized, instead leaving their users with a few tough questions: "How do we empower top scientists working in industry to lead science-minded positive change within their organizations? ... How do companies who seek genuine dialogue with this community engage?"

Barence writes "According to a Dell briefing given to PC Pro, 90% of company data is written once and never read again. If Dell's observation about dead weight is right, then it could easily turn out that splitting your data between live and old, fast and slow, work-in-progress versus archive, will become the dominant way to price and specify your servers and network architectures in the future. 'The only remaining question will then be: why on earth did we squander so much money by not thinking this way until now?'" As the writer points out, the "90 percent" figure is ambiguous, to put it lightly.