Hugh Pickens writes "Pulitzer Prize-winning science journalist Deborah Blum has an article in Slate about the US government's mostly forgotten policy in the 1920s and 1930s of poisoning industrial alcohols manufactured in the US to scare people into giving up illicit drinking during Prohibition. Known as the 'chemist's war of Prohibition,' the federal poisoning program, by some estimates, killed at least 10,000 people between 1926 and 1933. The story begins with ratification of the 18th Amendment in 1919, which banned sale and consumption of alcoholic beverages in the US. By the mid-1920s, when the government saw that its 'noble experiment' was in danger of failing, it decided that the problem was that readily available methyl (industrial) alcohol — itself a poison — didn't taste nasty enough. The government put its chemists to work designing ever more unpalatable toxins — adding such chemicals as kerosene, brucine (a plant alkaloid closely related to strychnine), gasoline, benzene, cadmium, iodine, zinc, mercury salts, nicotine, ether, formaldehyde, chloroform, camphor, carbolic acid, quinine, and acetone. In 1926, in New York City, 1,200 were sickened by poisonous alcohol; 400 died. The following year, deaths climbed to 700. These numbers were repeated in cities around the country as public-health officials nationwide joined in the angry clamor to stop the poisoning program. But an official sense of higher purpose kept it in place, while lawmakers opposed to the plan were accused of being in cahoots with criminals and bootleggers. The chief medical examiner of New York City during the 1920s, one of the poisoning program's most outspoken opponents, liked to call it 'our national experiment in extermination.'"

A few weeks back we discussed the perspective that the economic meltdown could be viewed as a global computer crash. In the NYTimes magazine, Joe Nocera writes in much more depth about one aspect of the over-reliance on computer models in the ongoing unpleasantness: the use of a single number to assess risk. Reader theodp writes: "Relying on Value at Risk (VaR) and other mathematical models to manage risk was a no-brainer for the Wall Street crowd, at least until it became obvious that the risks taken by the largest banks and investment firms were so excessive and foolhardy that they threatened to bring down the financial system itself. Nocera explores the age-old debate between those who assert that the best decisions are based on quantification and numbers, and those who base their decisions on more subjective degrees of belief about the uncertain future. Reliance on models created a 'false sense of security among senior managers and watchdogs,' argues Nassim Nicholas Taleb, who likens VaR to 'an air bag that works all the time, except when you have a car accident.'"

bjcarne writes in to commend Jon Ramvi and his team, who have delivered their first stable release of Ubuntu Eee, an Ubuntu version customized for the Asus Eee PC. "In December Ubuntu Eee started as a one man project, but [over] the last months several people have joined in on the development. We're trying to achieve something which [hasn't] been successful for any other Linux distribution yet: a OS targeting a single computer which includes the best applications available. This means people can buy this really cheap computer and easily get a great OS on it for free. Ubuntu Eee is just for the Asus Eee. Ubuntu Eee is smaller, faster and we're bringing people the cutting edge of technology (while being stable and free of course)."

chrplace forwards an article in which Gartner's Brian Lewis offers his perspective on what led to last year's Xbox 360 recall. Lewis says it happened because Microsoft wanted to avoid an ASIC vendor. "Microsoft designed the graphic chip on its own, cut a traditional ASIC vendor out of the process, and went straight to Taiwan Semiconductor Manufacturing Co. Ltd., he explained. But in the end, by going cheap — hoping to save tens of millions of dollars in ASIC design costs, Microsoft ended up paying more than $1 billion for its Xbox 360 recall. To fix the problem, Microsoft went back to an unnamed ASIC vendor based in the United States and redesigned the chip, Lewis added. (Based on a previous report, the ASIC vendor is most likely the former ATI Technologies, now part of AMD.)"

schliz alerts us that ISO, in response to the four appeals (Venezuela, India, Brazil, South Africa) filed in recent weeks, has put the OOXML standardization process on hold. Here is ISO's press release, which says that ISO/IEC DIS 29500 will not be published for at least "several months" while the appeals process goes forward.
Update: 06/11 10:13 GMT by KD : Reader Alsee points out that the fourth officially recognized appealing country is Venezuela, not Denmark as originally stated. The protests of Denmark and Norway are being disregarded, as they do not come from the administrative heads of their national organizations.