Slashdot Mirror

honestpuck writes "When reading the foreword of Rails Cookbook I felt a strong kinship with Zed Shaw, I too have fond memories of the first edition of Perl Cookbook and the way I relied on it once I'd taken the training wheels off. Since that one I have relied on several of the O'Reilly Cookbook series. It is only when I discard the early tutorial and dive in the deep end with a "cookbook" on my desk that I really start to learn proficiency." Read the rest of honestpuck's review. Rails Cookbook author Rob Orsini pages 514 publisher O'Reilly rating 7 reviewer honestpuck ISBN 0596527314 summary for programmers who know something about web development but are early in their use of Rails,

I felt timorous and unsure when I finished Agile Web Development with Rails, a marvelous tutorial that introduced me to my first real web development framework (I must have enjoyed it, I just bought the second edition). Since I have volunteered to develop a fairly large and complex web application in Rails I awaited the arrival of my copy of Rails Cookbook with hopeful anticipation and bated breath.

Rob Orsini, his fellow contributors (15 in all) and the team at O'Reilly have once again delivered. Compared to the previous titles in the series I've owned Rails Cookbook seems to have fewer recipes but as it is tackling an entire application framework and some serious issues, some of the solutions and discussions run a lot longer. The book is targeted at programmers who know something about web development but are early in their use of Rails, though it should be helpful to all Rails developers.

The book starts with tackling issues of installation and getting development tools installed in the first two chapters. Despite already deploying a couple of simple Rails apps I found that there was the odd useful tip in these chapters. The book then covers each of the three main sections of Rails; Active Record, Action View and Action Controller. The rest of the book goes on with large chapters on testing, Javascript, debugging, performance and hosting and deployment. Along the way it also covers REST, Action Mailer, security, plug-ins and graphics.

The extremely large section on Active Record was to me the most useful. I seem to spend an inordinate percentage of my Rails coding time with Active Record and it contains a large part of Rails power so I appreciated the size of this chapter. By contrast the chapter on graphics is almost entirely unread.

It seems obvious that this book should be compared to Pragmatic's Rails Recipes. The first point of difference is that Rails Cookbook covers installation and setup. The second point is that is 'Recipes' covers Rails 1.1 while 'Cookbook' targets the brand new Rails 1.2. As a project fairly new on the scene Rails is a fast moving target so the six months between the two books makes a difference. Both books have excellent coverage of the various aspects of Rails, with a great deal of overlap. 'Recipes' has more, shorter pieces while 'Cookbook' tends towards longer pieces with more discussion. 'Cookbook' is also more general, with more recipes more likely to be useful in every Rails project you write.

The style is different between the two. Here Cookbook comes off second best, it feels as though tightly edited by a number of hands and ends up lacking personality; functional but cold compared to Recipes. The writing, however, is good. It's easily read, at times it feels like a good textbook. The layout is clean, it is easy to find the information you need from each recipe when you want.

With almost all "cookbook" style books I seem to be left feeling that a number of the recipes are just a little too obvious and covered well in beginner tutorials. There is some of this in Rails Cookbook, most notably the first two chapters, but overall the book will be useful to any beginner to intermediate Rails programmer. Personally I had a couple of moments where I read a tip and wanted to scream as it demonstrated and explained in a few short sentences and half a page of code what had taken me hours to discover for myself.

The "Cookbook" series all seem to be books worth the price and shelf space. This one is no exception. I'd give it three out of five with an extra half for its timely information on Rails 1.2 and would recommend it for all Rails programmers from the absolute beginner through to all but the most experienced. If you already have a copy of 'Recipes' and are happy with it then you might want to stick with that till either volume is updated for the next major revision of Rails, otherwise you will almost certainly appreciate a copy of Rails Cookbook.

You can purchase Rails Cookbook from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Trent Lucier writes "Fellow programmers, beware! Graphic designers have been invading our territory. A flood of books have been released aimed at artists who want to learn web development skills. Oh, it starts innocently enough, usually with CSS and XHTML. But soon they are learning JavaScript, PHP, and even SQL! What have we techies fought back with? What material is there for us to boost our artistic right-brain power? Sadly, our motley collection of Gimp tutorials alone will not win this battle. We need something stronger. We need to understand the principles of graphic design. But the shelves have been empty of books that make this topic accessible to tech-minded people. Well, empty until now." Read below for the rest of Trent's review. The Principles of Beautiful Web Design author Jason Beaird pages 180 publisher O'Reilly Media rating 7 reviewer Trent Lucier ISBN 0975841963 summary A book aimed at developers who want to learn how to make websites look more attractive The Principles of Beautiful Web Design by Jason Beaird is aimed at developers who want to learn how to make websites look more attractive. The 5 chapters each cover one of the pillars of graphic design theory: Layout, Color, Texture, Typography, and Imagery. Full-color and packed with lots of great examples, the book contains screenshots from dozens of modern websites to illustrate graphic design principles. A cumulative case-study ends each chapter, where the author shows you how the theories he just explained can be applied to a real site he is developing for a client.

Except for some CSS sprinkled here and there, the book contains no code. Don't look for tips on creating 3-column layouts or other stylesheet wizardry, because you won't find it here. The author assumes that you know how to take an image mock-up and convert it into an HTML/CSS document. This is a strong point of the book, since the focus can remain on graphic design techniques and not unnecessary code listings Additionally, there isn't much discussion of tool usage. A few examples use Photoshop, but the book focuses mostly on theory and case studies, not step-by-step program tutorials.

The book starts with Layout and Composition. If you have ever wondered why some websites just look better organized than others, this chapter will explain why. Beaird discusses the concepts of grid theory, and how using the golden ratio to divide page elements can improve the visual appeal. Plenty of examples are given that illustrate the principles of balance, unity, and emphasis.

The Color chapter contains my favorite example, where Beaird uses different versions of the same drawing to describe monochromatic, analogous, and complementary colors. As with the previous chapter on layout, this part of the book does an excellent job of teaching you how to learn from attractive websites, instead of mindlessly imitating them. Color is a hard topic to understand, but there are some good tips here that teach readers how to create an appealing palette for a website.

Relying solely on solid colors and grid layouts can make a website look flat. The Texture chapter discusses ways to use style and make your designs much more eye catching. This chapter is probably the most "Web 2.0" chapter in the book. Gel buttons, gradients, and backgrounds are all discussed.

To the dismay of typophiles everywhere, font support on the web is very poor. There are very few "web safe" fonts that designers can safely assume are on all computers. The Typography section shows readers how to make the most out of this situation by understanding letter spacing, justification, and font usage. Beaird also discusses the sIFR technique (Scalable Inman Flash Replacement), which uses Flash and Javascript to display fonts that may not be on the user's computer. The sIFR method is accessible and degrades gracefully. While the book does not discuss the specific implementation details of this method, just bringing it to my attention taught me something new.

Imagery is the subject of the final chapter, and the book ends on a disappointing note. Very little of this section is about the graphic design principles behind imagery. Rather, precious pages are dedicated to discussing various license agreements and tips on finding stock photos. This is useful information, but it should have been relegated to a sidebar at the most. The chapter focuses almost entirely on images as content and not as design elements. If you want to know how to make images in a blog post look pretty, there are some ideas here (drop-shadows, borders). But there is no information about how to work images into a page header or navigation menu. How do I determine if an image matches my color scheme? How can images spice up a design without going overboard? These were just some of the questions I had going into this chapter that were left unanswered. The Texture chapter hinted at these ideas with examples, but I wanted to see a deeper explanation of the underlying principles.

The book is a little short at 180 pages, but that's not as bad as it may seem. Those of us accustomed to reading 800-page tomes on programming tend to forget how much content can be packed into a book when the author doesn't have to waste 300 pages listing code, 200 pages on the API, and 150 pages on an index.

The Principles of Beautiful Web Design is a good book to kick start your graphic-design journey. The biggest benefit that I got from this book is the knowledge to learn from great designs as opposed to just admiring them in a state of awe. The book could have been a little longer, and some of the topics could have been discussed in more detail. This book won't teach you everything, but it's a good place to start and it will leave you excited about learning more.

Trent Lucier is a software engineer. He is the creator of ChessUp, a tool for creating chess diagrams online.

You can purchase The Principles of Beautiful Web Design from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Fennec writes "Amazon.com has launched a beta of a new service called Askville, yet another online answers service, flavored with "Experience Points, Levels, and Quest Coins." These coins will supposedly become useful some day on another Amazon service that's not actually open yet, Questville. If this virtual currency becomes useful, could Askville fill a place between strictly volunteer systems and pay-for-answer services like the now-defunct Google Answers? Or is it destined to fail in the already-saturated online Q&A market?"

Fennec writes "Amazon.com has launched a beta of a new service called Askville, yet another online answers service, flavored with "Experience Points, Levels, and Quest Coins." These coins will supposedly become useful some day on another Amazon service that's not actually open yet, Questville. If this virtual currency becomes useful, could Askville fill a place between strictly volunteer systems and pay-for-answer services like the now-defunct Google Answers? Or is it destined to fail in the already-saturated online Q&A market?"

An anonymous reader writes "On December 23, Amazon advertised a 'buy one get one free' sale on DVD box-sets, but apparently did not test the promotion before going live. When anyone placed two box-sets in their cart, the website gave a double discount — so the 'grand total' shown (before order submission) was $0.00 or some very small amount. Despite terms stating that Amazon checks order prices before shipping, Amazon shipped a large number of these orders. Five days later (December 28), after orders had been received and presumably opened, Amazon emailed customers advising them to return the box-sets unopened or their credit cards would be charged an additional amount (more threads). Starting yesterday, Amazon has been (re)charging credit cards, often without authorization. On Amazon's side, they didn't advertise any double discount, and the free or nearly-free box-sets must have cost them a mint. But with Amazon continually giving unadvertised discounts that seem to be errors, is 'return the merchandise or be charged' the new way that price glitches will be handled?"

RadioTV writes "Amazon is in Beta testing with select Tivo users to allow Unbox videos to be downloaded to Series 2 and 3 set-top boxes. The FAQ for the service is available." The price point for movies is fairly reasonable. No HD and won't work with DirecTV's obsoleted HD tivo, but this is a step in the right direction.

RadioTV writes "Amazon is in Beta testing with select Tivo users to allow Unbox videos to be downloaded to Series 2 and 3 set-top boxes. The FAQ for the service is available." The price point for movies is fairly reasonable. No HD and won't work with DirecTV's obsoleted HD tivo, but this is a step in the right direction.

Techno-Canuck asks: "Now that the DLP TVs have been in customers' hands for the last few years, there are problem histories that are begining to unfold. According to Toshiba's DLP TV User Manual: 'The average useful service life for the lamp is approximately 8,000 hours in LOW POWER or 6,000 hours in HI BRIGHT MODE.' However there were problems with certain 2005 Toshiba models that saw the lamp lifetime at only a few hundred hours or less. Toshiba replaced the lamps in these models at no cost and extended the lamp warranty to 2 years. According to an FAQ on About.com the lamps currently last an average of 1500 hours. Whether or not Toshiba has resolved the problem remains to be seen, as only time will give the real indication. There also seems to be lamp issues with some 2004 models as well, but Toshiba does not seem to be stepping forward to resolve the issues in this case. The customer ire is starting to rise, however. Will there be similar problems for the 2006 models once enough time has elapsed?" Most people probably would use the information provided by Toshiba to make a decision about what the lamp maintenance costs would be for DLP ownership. However if lamps only last for 1500 hours, then that's a 400% increase in costs over what Toshiba is presenting to customers. The cost of a lamp is $200 or more, and for a family household that averages 6 to 8 hours of TV viewing per day, this translates to a new lamp every 187 to 250 days. Strangely enough the Toshiba warranty on a replacement lamp not covered by the original TV warranty is 180 days.

It's possible that the death blow has already been struck. It appears that no longer carries DLP TVs in its product line."

simoniker writes "Gamasutra has just posted an interview with author Gerard Jones, subtitled 'Sex, Violence, Tension and Comic Books,' in which the writer of 'Killing Monsters' talks about violence and games eloquently. When asked: 'What do you think it is in your work that resonates with the gaming community?', Jones comments: 'Video games have been so much under attack recently, that I think there's a certain nervousness. Most people in this business are very pleasant and non-confrontational and the fact that they are being reviled as the causes of crime, causes of violence, is disturbing. On the one hand, I think people want to know how to respond to those criticisms. But on the other hand, I think there's some genuine anxiety that maybe games have a bad side, maybe there is a problem, and how do we deal with any guilt or fear?' He goes on to suggest of attacks on gaming: "I would say now we're kind of at the tail end. If games continue to push boundaries, particular ones could come under attack. A lot of it's just the medium being around long enough that people have realized the world hasn't gone to hell.""

An anonymous reader writes "As 'Black Friday' approaches and consumers line up for the Playstation 3 it looks like Zune has become an afterthought. Despite months of hype, opening Zune sales are only so-so. While Zune did reach the top 10 on Amazon's Top 25 list for electronic product sales on its first day, it quickly fell below the top 15 and continues to drop. Six separate iPod models now outsell it as well as SanDisk's e250 player. In-store sales are not much better."

mdf356 asks: "It's been 5 years since I left graduate school and started designing and writing software for a living. After 5 years of writing operating systems code, I feel like I've forgotten some of the more advanced data structures I used to know. The next time an interesting problem arises, I'd like to have more in my toolbox than hashes, linked lists, heaps and various binary and n-way trees. I'd like something short and sweet, more in the line of the standard C book. Algorithm Design by Kleinberg and Tardos looks likely to be too basic, but I haven't read it (I'd like to avoid paying $90 for something that won't meet my needs). CLR is far too large and almost exclusively covers basic territory. Tarjan's Data Structures book looks like it has potential, but seems focused on network algorithms, which are unlikely to be applicable to the kernel programming I do. What are some good reference books on more advanced data structures and algorithms, particularly ones with potential applicability to an operating systems kernel?"

mdf356 asks: "It's been 5 years since I left graduate school and started designing and writing software for a living. After 5 years of writing operating systems code, I feel like I've forgotten some of the more advanced data structures I used to know. The next time an interesting problem arises, I'd like to have more in my toolbox than hashes, linked lists, heaps and various binary and n-way trees. I'd like something short and sweet, more in the line of the standard C book. Algorithm Design by Kleinberg and Tardos looks likely to be too basic, but I haven't read it (I'd like to avoid paying $90 for something that won't meet my needs). CLR is far too large and almost exclusively covers basic territory. Tarjan's Data Structures book looks like it has potential, but seems focused on network algorithms, which are unlikely to be applicable to the kernel programming I do. What are some good reference books on more advanced data structures and algorithms, particularly ones with potential applicability to an operating systems kernel?"

mdf356 asks: "It's been 5 years since I left graduate school and started designing and writing software for a living. After 5 years of writing operating systems code, I feel like I've forgotten some of the more advanced data structures I used to know. The next time an interesting problem arises, I'd like to have more in my toolbox than hashes, linked lists, heaps and various binary and n-way trees. I'd like something short and sweet, more in the line of the standard C book. Algorithm Design by Kleinberg and Tardos looks likely to be too basic, but I haven't read it (I'd like to avoid paying $90 for something that won't meet my needs). CLR is far too large and almost exclusively covers basic territory. Tarjan's Data Structures book looks like it has potential, but seems focused on network algorithms, which are unlikely to be applicable to the kernel programming I do. What are some good reference books on more advanced data structures and algorithms, particularly ones with potential applicability to an operating systems kernel?"

mdf356 asks: "It's been 5 years since I left graduate school and started designing and writing software for a living. After 5 years of writing operating systems code, I feel like I've forgotten some of the more advanced data structures I used to know. The next time an interesting problem arises, I'd like to have more in my toolbox than hashes, linked lists, heaps and various binary and n-way trees. I'd like something short and sweet, more in the line of the standard C book. Algorithm Design by Kleinberg and Tardos looks likely to be too basic, but I haven't read it (I'd like to avoid paying $90 for something that won't meet my needs). CLR is far too large and almost exclusively covers basic territory. Tarjan's Data Structures book looks like it has potential, but seems focused on network algorithms, which are unlikely to be applicable to the kernel programming I do. What are some good reference books on more advanced data structures and algorithms, particularly ones with potential applicability to an operating systems kernel?"

andrewl6097 writes "Amazon.com has launched it's Amazon Unbox video store. Looks like about 1300 movies and 350 tv series, at $9.99 and up for movies and $1.99 per TV episode. Downloads come with a DVD quality version and a version more appropriate for portable players (using Windows DRM). Also, videos can be re-downloaded from your Amazon media library. Cool!"

Jewfro_Macabbi writes, "Recently after browsing major online retailers for Bluetooth adapters, I went to Amazon.com to find front-page ads for, you guessed it, Bluetooth adapters. Disable cookies, the ads go away; re-enable cookies and the ads re-appear. The EULA is ambiguous as usual. Try it for yourself and see."

RebornData writes "I receieved an e-mail this morning inviting me to participate in a limited beta of Amazon EC2: the Amazon Elastic Compute Cloud. It's a grid computing service that allows you to create and upload your own Linux-based machine images and run them in Amazon's system, starting at $.10 per "instance hour" (each machine instance being equivalent to a 1.7GHz Xeon with 1.75GB of RAM, and 160GB disk). You can use their tools to create and start new instances dynamically to meet whatever your particular capacity needs are at any given moment. Fedora Core 3 and 4 are explicitly supported, but any distro based on the 2.6 kernel should work. The service documentation provides more technical details. Unfortunately, it appears that the beta is limited to existing Amazon S3 users, and is already full."

RebornData writes "I receieved an e-mail this morning inviting me to participate in a limited beta of Amazon EC2: the Amazon Elastic Compute Cloud. It's a grid computing service that allows you to create and upload your own Linux-based machine images and run them in Amazon's system, starting at $.10 per "instance hour" (each machine instance being equivalent to a 1.7GHz Xeon with 1.75GB of RAM, and 160GB disk). You can use their tools to create and start new instances dynamically to meet whatever your particular capacity needs are at any given moment. Fedora Core 3 and 4 are explicitly supported, but any distro based on the 2.6 kernel should work. The service documentation provides more technical details. Unfortunately, it appears that the beta is limited to existing Amazon S3 users, and is already full."

RebornData writes "I receieved an e-mail this morning inviting me to participate in a limited beta of Amazon EC2: the Amazon Elastic Compute Cloud. It's a grid computing service that allows you to create and upload your own Linux-based machine images and run them in Amazon's system, starting at $.10 per "instance hour" (each machine instance being equivalent to a 1.7GHz Xeon with 1.75GB of RAM, and 160GB disk). You can use their tools to create and start new instances dynamically to meet whatever your particular capacity needs are at any given moment. Fedora Core 3 and 4 are explicitly supported, but any distro based on the 2.6 kernel should work. The service documentation provides more technical details. Unfortunately, it appears that the beta is limited to existing Amazon S3 users, and is already full."

theodp writes "USPTO documents released Thursday show that Amazon is seeking a patent covering subscription-based shipping, aka Amazon Prime. Among the seven listed inventors is Amazon CEO Jeff Bezos, who has been singing the praises of Amazon Prime to Wall Street."

The same technology and silicon and 3D algorithms we play around with every day are about to invade medicine. The following is an excerpt from Andy Kessler's new book, The End of Medicine: How Silicon Valley (and Naked Mice) Will Reboot Your Doctor. CT Anxiety I always feel a certain anxiety when I walk into the Hyatt Regency at the bottom of California Avenue in San Francisco. The cutsie Trolley car outside, the Embarcadero tile pattern on the sidewalk — they are all part of the package. But as I've done every time I've been there, I head straight into the lobby, tilt my head back and scan the Escher-like floors, starting at the top and then down and outwards to the bottom until I start feeling dizzy. I thank Mel Brooks for this.

With my head spinning from this "High Anxiety" flashback, I stroll into the conference, half expecting to be given a barium enema by a cross between Nurse Diesel from Mel Brooks' flick and Nurse Ratched from One Flew Over The Cuckoo's Nest. I really gotta switch to decaf on days like this.

The 7^th International Multi-Detector Row Computed Tomography Symposium sounded innocuous enough. I assumed it would be a bunch of technical papers on the future of scanning, where I would read the paper in the darkened hall until lunchtime and then head off for some hot Hunan and home.

Instead, the place was like a carnival for cardiologists. Talk about feeling like a fish out of water. Outside the hall was an expo of sorts, with big signs flashing Toshiba and Philips. Instead of TVs or microwave ovens, there were PCs with 3D models of some poor schmuck's diseased coronary arteries being folded, stapled and rotated.

The back wall of Toshiba's booth caught my eye and I just stared at it. Rule number one at any tradeshow booth is never look interested or you are doomed to a rapid-fire ten-minute lecture on the ins and outs of the product and forced to give up your card as a qualified lead, to be hounded by phone, fax, email and snail mail for the next year.

"Those are our detectors." Damn, I was snagged.

"They look like the display on my laptop," I noted.

"Well sure, they are not that much different from a flat-panel display."

"Same economics making them?" I asked. Flat panels are notoriously expensive to manufacture, because of their size, unlike chips, where hundreds can fit on an eight-inch diameter wafer.

"Oh no, as we go from 4- to 16- to 64-slice, the detectors can be manufactured discreetly and butted up against each other. We don't have yield issues."

"How much is one of these 64-slice scanners?" I asked.

"Are you ready to buy one today, or this month?" booth-guy asked me.

"No, no, although I wouldn't mind one in my garage. I'm a tech guy."

"Oh, OK. Well, these are basically one- or two-million dollar machines."

"Wow." I wasn't sure if that is a lot or a little, but often a well-placed 'wow' gets you all sorts of inside scoop.

"I know, pretty cheap. We think we have a variety of advantages over the competition and you will see in the face-off that ..."

"Why so much? I've been in enough factories, and those flat panels are a couple of hundred bucks each and the motor to rotate can't be more than ..."

"Well, the X-Ray source is not inexpensive."

"What? Hundreds of thousands of dollars?" I trolled.

"Probably not. We do have high selling expenses. When you only sell a hundred of anything, there is lead generation and a sales pipeline and funnel."

He started whispering. "They could be a lot cheaper." He must be having a tough month.

"Don't let me stop you, by the way," I said, looking around, trying to imply he should hard sell some of these cardiologists and radiologists who were buzzing around the display.

"Doctors aren't buyers, not for these machines. We sell to a few clinics. The rest is into hospitals - they are the only ones that can afford them for now."

"But you said cheaper — I mean, these can be in the hundreds of thousands of dollars instead of millions." It was a statement dressed up as a question.

"Someday," he whispered, again.

That's all I needed to know.

Several times, I heard references to the big face-off that afternoon, like it was the reason everyone was there. "Don't miss the face-off," "This ought to show well at the face-off," "This year is going to be so much better than last year's face-off." OK, I get it.

I sat down in the auditorium and the talks and dim lights put me right to sleep.

The head whips woke me up, as my neck turned into Jello and my chin dug into my chest. I wasn't sure if I was awake, my heart was beating fast - I was on the top floor looking over the rail next to Mel Brooks ... Nope, I'm OK, I'm awake, although embarrassed as quite a few radiologists turn to see what the commotion was in my seat.

"Ladies and gentlemen, welcome back, take your seats, fasten your seatbelts, this is going to be exciting. I am pleased to announce that for our 3^rd Annual Workstation Face-off, we have five different vendor groups competing — well, facing off. We have five different data sets: brain, runoff, lung, colon and heart."

The room exploded in applause, like this was some sort of important revelation.

"On the stage, we have workstations from GE Healthcare. Dr. Gruden, please take a bow. Also Vital Images, Philips Medical Systems, Siemens Medical Solutions and TeraRecon. May the best workstation win. Let's get started."

The room was buzzing. On stage were two giant screens. On the left was a view from the monitor of the workstation and on the right was a live feed from the operator's keyboard and mouse so the audience could see how many clicks and keystrokes and other contortions are needed to get through the data set.

"OK, let's start with the brain. GE, you have six minutes for both the Angiogram and the Perfusion. Go."

A giant clock on stage started counting down from 6 minutes. The doctor operating the GE workstation was furiously clicking and slapping his mouse around and on screen; we all could share his view zooming through someone's brain.

"OK, we can see the internal carotid artery on the right-hand side, so now let's quickly move over to this area on the left, ah, not hard to find, there it is, we see the ICA stenosis, let's measure it, 63% blockage." A smattering of applause. "We can zoom in and clearly delineate the calcified vs. the soft plaque." More applause.

"OK, let's quantify the infarct core ..."

I was transfixed. This guy was zooming through someone's brain like it was a Sunday drive. More like a Sunday afternoon video game. I kept looking for a brain in a jar of formaldehyde labeled "Dysfunctio Cerebri — Abnormal Brain" and Dr. Frankenstein's assistant Fritz limping back to the laboratory.

"Let's mark this tissue at risk for infarction and measure some things while we are over in the left cerebral - OK - MTT is 86.7, TTP let's call it 52.5 ..."

He zoomed around the brain like it was just a bunch of bits on the screen, which of course it was. Duh.

"OK. Time. 5 minutes 32 seconds. Very nice. Thank you," the moderator said. The place went crazy. This was repeated on each of the workstations by different doctors to often-thunderous applause. I had a mild headache from all the excitement.

I watched these workstations find aneurysms in the arteries from the waist down, the run off. The trick is to remove the bones from the view and be left with just the arteries. Jeez, everyone knows that. Even I could find the mild aneurismal dilation of right renal arterial trifurcation! But my feet started to hurt and I looked around and lots of folks were rubbing their calves.

In the lung, the fly-throughs were looking for lobe nodules, which weren't so obvious. It was a maze of tubes in there — who can even find their way, let alone in under 4 minutes? But sure enough, there was the posterior and the one adjacent to the heart. Each of the five operators then went back and compared them to a study from three years earlier, after finding them in the previous study, of course. Pretty cool. Does my doctor have this? I coughed, more of an unconscious reflex than anything else.

"OK, a perennial favorite, let's move on to the bowels. This year's virtual colonoscopy will require identifying and measuring five different polyps as well as comparing supine and prone data sets to differentiate stool from polyps."

There was a gasp from the crowd, probably from all the men over 50 who have not-so-fond memories of their real colonoscopies.

"The folks from TeraRecon will go first." "Thank you. For this data set, we have decided to show off our handheld interface device. It is a two-handed device, requiring minimal keyboard usage."

On the right-hand screen, the view zoomed into the doctor's hands wrapped around what looked like a Nintendo or Sony Playstation controller. He was banging it and twisting it around, not much different than my kids playing Halo 2. Except that on the left-hand screen, instead of you as Master Chief blowing away the Covenant to stop them from destroying Earth, you are Master Doctor searching for cancerous polyps extracting revenge and trying to destroy your patient. Or something like that. And you only have six minutes and a crowd of a thousand to cheer you one.

"OK," the doctor running the TeraRecon station said, "let's go into C.A.D. mode to navigate through the colon."

On screen, the screen started flying through the wrinkled walls of the colon, twisting and turning, to the left, sliding over, turning up, then right, around a corner, then down again until it saw something abnormal and stopped in front of a hanging polyp. Ah, that's what Steve Sandy was telling me about.

Massive applause.

TeraRecon found all the polyps and so did everyone else. It wasn't hard, those polyps hung like fruits from a tree, pretty obvious against the background of the empty colon. Each of the operators had to go to the alternate data set to show that a few potential polyp looking globes were nothing more than a pile of, well, stool.

My cough had mysteriously turned into a pain in my lower gut.

"Now, what you have all been waiting for, the grand finale, someone left their heart in San Francisco."

On screen was a giant rendering of a heart and most of the coronary arteries. It might as well have been pumping and spraying blood all over the audience like the movie Carrie, there was such a frenzy.

Each of the workstations zoomed in, probed for diameters of sinotubular junctions and aneurismal sinuses. Ho hum. But in no time, each found blockages, stenosis that either had already caused a heart attack or was about to any day.

I just stared at the screen. My eyes were wider than Marty Feldman as Igor in Young Frankenstein. It's not some dream of the future, there it is in front of my face. I felt some pains on the left side of my chest, but my stomach ache went away.

This is it. The resolution was high enough, and there was plenty of speed to zoom around and find all the gunk in less than five minutes. These guys could peak inside and tell me if I was going to have a heart attack, before I do, before I drop on the floor grabbing my chest and my wife screams to the 911 operator to get someone there as fast as they can, before all my relatives get the call saying Andy has had a heart attack, before I get overloaded with blood thinners and can't remember what day it is.

This changes everything. Blood pressure readings, cholesterol checks for low-density lipoproteins, echocardiograms, all that stuff is primitive stuff, like silent movies — OK, another Mel Brooks reference. It just has to be cheap enough and it will be as routine as the doctor banging your knee or squeezing the crowned jewels.

Let's see: $2 million machine, 5 minutes per patient, of course, that means 144 a day, 720 per week, 36,000 per year, hmmm, that's $55 per scan. Add a little for the attendees and five minutes of the radiologists time and voila, maybe this is a mass market thing after all.

Andy Kessler is a former Bell Labs chip designer, turned Wall Street analyst and hedge fund manager turned author. Sounds like he can't keep a job. See this book's page at Amazon.

miahrogers writes "The IRS Scam from a few weeks ago was not the the usual canned phishing attack; it exploited a vulnerability in the IRS benefits website to make users think they were at a government site. Also, according to Infoworld, eBay's own fraud team was tricked into thinking a phishing email was legitimate eBay correspondence. Mix the above IRS exploit with a phony email and you have misplaced trust that foils even professional fraud teams. Interestingly enough, the newest addition to my bookshelf predicted these attacks in full detail. From chapter 4: 'Combined with vulnerable Web servers allowing the "trusted" domain to launch the attack, it will be harder to determine whether the email is or isn't legitimate. When a person turns in the e-mail to question its legitimacy, due to the known marketing campaign a tech support representative may overlook the fraud report and tell the customer that XYZ company did send out such a marketing e-mail and it is OK to click the links.' Are phishers using this book as a tool, or is it a legitimate prediction? As an IT professional, what efforts should our corporate IT department be making to proactively to eliminate these vulnerabilities?"

Joey Braff writes "Many of you have probably heard of the famous BOG - BIOS Optimization Guide. For those who have not, make sure you take a look at this mega-guide with more than 300 BIOS settings and they just added 10 more! If you doubt its authenticity, note that its author is a doctor and the guide is also available as a book."

StWaldo writes "Amazon.com has added a 'ProductWiki' to some of their item pages. Wikified items seem to be limited to certain categories, DVDs being one un-wikied realm. Adding Wikiness to the site is just the latest in new participatory activities Amazon has adopted, along with tags and customer discussions." From the article: "So Amazon's gradually allowing you, along with your Wish List, your purchases, your clickstream, and, if you sell anything on Amazon, how good your reputation is--to build up a pretty detailed database of what you like (or don't) and what's important to you. I don't know what Amazon will do with this--fortunately, it seems to have a pretty light touch with how it uses what it knows about you--or what it will allow us to do with all this data. But as it grows, it could become a pretty powerful profile."

StWaldo writes "Amazon.com has added a 'ProductWiki' to some of their item pages. Wikified items seem to be limited to certain categories, DVDs being one un-wikied realm. Adding Wikiness to the site is just the latest in new participatory activities Amazon has adopted, along with tags and customer discussions." From the article: "So Amazon's gradually allowing you, along with your Wish List, your purchases, your clickstream, and, if you sell anything on Amazon, how good your reputation is--to build up a pretty detailed database of what you like (or don't) and what's important to you. I don't know what Amazon will do with this--fortunately, it seems to have a pretty light touch with how it uses what it knows about you--or what it will allow us to do with all this data. But as it grows, it could become a pretty powerful profile."

Hemos writes "Most of the books sent to Slashdot for review have words like "Java", "hacks", or "802.11b" in the title, but occasionally an odd general book arrives after a publicist hits the wrong button on the keyboard. At first, I thought that John Hodgman's The Areas of My Expertise , was a mistake, but now I'm not sure. Because this is Slashdot, I'll spend the rest of the review wondering whether the Internet is really changing jokes, humor in general, and even all narrative form. But before that, I can tell you now that there's something sly, odd, and very funny about the book even though it is little more than a disconnected collection of lists and details. It's a coredump from a mind filled with 700 names of Hobos, the ways to use a ferret to rob a bank, the secret to winning every fight (use henchmen!), and the first draft of T.R. Roosevelt's famous command: speak softly and pierce their eyes with a golden hook." Read on for Peter Wayner's review. The Areas of My Expertise author John Hodgman pages 230 publisher rating 8 reviewer Peter Wayner ISBN summary

Let me help the curiosity of the general reader before I get to the meat of the review where I reveal enough Internet-releated theories to satisfy the nasty trolls who like to wonder why Slashdot is wasting valuable bits on silly topic. As John Hodgeman is fond of promising on his book's cover: "THE ANSWER IS PROVIDED".

The book is said to be a relatively complete collection of all of the important expertise in the mind of John Hodgeman, the author referred to on the cover as "A PROFESSIONAL WRITER." There's one section that contains the "700 Hobo names you requested." ("Irontrousers the Strong", "Fleastick" are 55 and 79). Another includes random crap about the 50 states. The sections are all very silly and the humor emerges from a form of metaphysical misdirection. I still chuckle when I think about the list of jokes that "have never produced laughter." The jokes really aren't funny, but there's something insane in their very deliberate and plodding failure.

The book can be sampled like a box of chocolates. I tried to read it through directly to see if any grand arc emerged, but my mind couldn't extract any great signal from the cultural noise. For all I know, he wrote each bit on an index card and then shuffled the cards before typesetting the book. The gags are all about the randomness of the wrong information cluttering his minds and, to a large extent, the texture of the words.

Long ago, an editor would have thrown this guy out on his ear for even suggesting that 230 some pages of chuckles would be worthy of getting people together for a book publication party. I don't think the editor or the publisher let those worries get in the way.

Which brings us to the answer I owe you about why this is a post- internet book. As the non-funny "unified theory of the web" in Small Pieces Loosely Joined pointed out, the web is made up by many small pieces of information arranges with hyperlinks that join them, loosely if you will. Well, that's this book. Random pieces of crap, given an additional shuffle to make it seem all the more random. It's all very loosely joined.

Long ago, professional writers like John Hodgman included narrative arcs and well-wrought plotlines with their books. Perhaps we don't need them any more. Maybe the Internet has changed our brain and made us happy to graze from the bar without the need of a sitdown meal. To put on my PROFESSIONAL POSTER hat, I think that the Internet has made us accustomed to getting our stuff in loosely joined pieces.

In fact it's worse than that. Most bloggers write complete paragraphs, but many parts of the book are just a collection of tiny bits that don't even qualify as full paragraphs. Many of the entries are just lists and many of the items in these lists aren't even complete sentences. This modern approach to writing is everywhere. Even the old dead-tree-based print media is producing magazines filled with so-called stories that are nothing more than lists of cool things to do, watch, or eat. The high-toned magazines may even have two or three sentences per list item--enough, I guess, to qualify as a paragraph, but most are nothing more than lists.

Some folks seem to feel that this fragmented, attention-deficit- whatever life is a good thing. Steven Johnson, for instance, argues in his book that the jumpy plots made of many short scenes are evidence of an expanding intellect. Modern TV seems almost unwatchable to me. But I also find old Starsky and Hutch episodes to be terribly plodding. Won't they just get to the point and catch the killers? But, back then, the journey was 9/10ths of the fun. The point wasn't really the point.

But maybe I'm just making too much of it. Plenty of comedy has always been filled with short pieces. Steve Martin's Cruel Shoes , for instance, was broken into a number of very short bits, although there really were a few threads woven throughout the book. Absurdist comedy like Monty Python's Flying Circus was just a collection of wacky riffs, but they did try to come up with clever and even more absurdist segueways to carry the viewer from scene to scene. It was not usual to have a bunch of guys walk into the frame of a sketch and carry one or more of the characters off and into the frame of another set.

At this point, I sort of feel that I need to add what PROFESSIONAL WRITERS call a "kicker", some sort of question or twist that connects us with the top of the piece and gives the reader a sense of closure. They're hard to find and even harder to craft. Ones that are even slightly funny or insightful can get you promoted. But, given the spirit of the book, I feel inclined to invoke the spirit of a hobo, slack a bit, and steal the ending from the book itself. (I can do this without spoiling the book for you!) As Hodgman writes when he comes to the end of the deck of joke cards, "That is all."

You can purchase The Areas of My Expertise from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

roelbj writes "For those Star Trek fans wondering what to ask for this Christmas, you may wish to consider The Ultimate Star Trek Collection to be released on November 15. For just (cough) $2499.99, you'll get 212, count them, 212 DVDs with everything ever produced under the name, including all seasons of all five telvision series as well as the ten feature films. Before loading up your disc changer and hitting play, remember to get up once in a while."

Nuclear Elephant writes "After six months of development, DSPAM v3.6 has been released. The most notable change is the series of new features added to make an anti-spam gateway appliance possible (Knoppix anyone?). Version 3.6 also includes a highly accurate alternative to Bayesian filtering known as Markovian discrimination, based on Bill Yerazunis' research. Other significant enhancements include trusted sender whitelisting, integrated Clam Antivirus and LDAP support, a centralized spam training alias, and a new dependency-free storage driver. Much of the documentation has also been rewritten to make installation easier. A change log and release notes are also available. Slashdot has recently featured a review of the author's book, Ending Spam and an interview as well."

joemite writes "As every Browncoat knows, Serenity, the motion picture based on the Firefly series opened today. For the uninitiated, Serenity is based on the short-lived Fox television show Firefly (created by Joss Whedon, [Buffy the Vampire Slayer]), which follows a group of outlaws in a unique space-western universe. While there are no aliens or temporal anomalies, the stage is set for our group of heros to out-wit and out-strategize the giant and evil Alliance. Go out and watch the movie this weekend and see why the Firefly series is an Amazon.com best seller." If you're on the fence, reviews available at SFGate, Wired, the Seattle Times, and IGN.

coaxial asks: "So it's that time again to consider taking the GRE. While there are many resources on the web about the general test (mostly vocabulary building), the computer science subject test seems to be lacking. This is a shame, since this test covers pretty much everything in the undergrad curriculum. So I ask the grad student readers of Slashdot: what resources, besides the one book I've found, did they use."

stern writes "In the not-so-distant past, engineers, scientists and mathematicians routinely consulted tables of numbers for the answers to questions that they could not solve analytically. Sin(.4)? No problem: look it up in the Sine table. These tables were prepared by teams of people called computers (no, really -- that's where the term comes from) who typically had only rudimentary math skills. The computers were overseen by more knowledgeable mathematicians, who designed the algorithms and supervised their work." Read below for Stern's review of David Alan Grier's book When Computers Were Human. When Computers Were Human author David Alan Grier pages 424 (with index and table of names) publisher Princeton University Press rating worth reading reviewer Stern ISBN 0691091579 summary A history of the first "computers", semi-literates who did math by hand

The most important of these teams was the Mathematical Tables Project, organized by the Work Projects Administration in the United States during the Great Depression. WPA rules required the hiring of people with virtually no skills, so much of the definitive work of the Mathematical Tables Project was computed by people who had mastered only addition. They were not authorized to subtract, let alone delve into the mysteries of multiplication or division. The algorithmic steps assigned to them sometimes produced negative numbers, and it goes almost without saying that these computers had no idea what these were or how to handle them. Gertrude Blanch, the mathematician who oversaw their work, had devised a scheme whereby positive numbers would be written in black, negative numbers in red. On the wall in front of her human computers hung a poster that encapsulates much of the era of human computing. It read:

Black plus black is black
Red plus red is red
Black plus red or red plus black, hand the sheets to team 2

Grier has written a history of human computing. It begins in the 1760s and continues through the two hundred years until digital computers ended the industry.

From the start, computers were dedicated to projects in astronomy, cartography, and navigation. Grier describes the nature of these problems and why they required numerical solutions. He touches on the alternating competition and cooperation between teams of computers in different countries, and the different organizational models they employed. Perhaps the most memorable fact from the early years of human computing is that the very first team of French computers, assembled by Gaspard Clair Francois Marie Riche de Prony in the early 1790s, was composed entirely of wig-makers left unemployed by the French Revolution. They created trigonometric tables required by France's experiments with the decimalization of trigonometry (an abandoned effort to do for angle measure what the metric system was doing for the measurement of mass, length, and so forth).

Their work, though of little ultimate relevance to the modern world, illustrates aspects of human computing that would not change. Major computing efforts were always sponsored by governments. A small number of planners oversaw work by people who themselves knew little math. And the bulk of the work was done by people who were marginalized, perhaps otherwise unemployable, and who would do the repetitive calculations. This work conferred no prestige, and many were skeptical even of the conclusions drawn from it. If an equation could not be properly solved, how could one take confidence from any numerical approximation? Even Henry David Thoreau worked a dig at human computers into the manuscript for Walden, dismissing the mathematics that might allow an astronomer "to discover new satellites of Neptune but not detect the motes in his eyes, or to what vagabond he is a satellite himself."

Women emerged as the most important computers. Demand for computing spiked in wartime, when young men were off fighting and therefore unavailable, and the economics of hiring women was compelling even in peacetime. They would work for half of what similarly skilled men would. By World War II, in the United States, computing power was measured not in megahertz or teraflops, but in kilogirls.

By the 20th century, the work of human computers was augmented by mechanical or even electrical calculators that automated certain steps of their work, but these were expensive and prone to breakdown, and did not significantly change the nature of the work.

Grier devotes special attention to the Mathematical Tables Project run by the WPA, later taken over by the National Bureau of Standards, and to the mathematician Gertrude Blanch who ran that team. She is fascinating, a woman who arrived in the United States at the age of 11, who had worked to support her family and not been able to get her Ph.D until she was 39 years old. It was then 1936, the middle of the Great Depression, and the job prospects for female, Jewish mathematicians were bleak. Through luck and hard work she found her way to the Mathematical Tables Project, where she assumed a role that combined mathematician, schoolteacher, and coach. Her fanatical attention to error-checking resulted in tables good enough to win the support of those who were skeptical of work by a government relief organization. She also led by example, and solved certain problems personally when she thought that would be easier than breaking down the algorithms for her computers. Grier says that Blanch in this way personally did work that backed Hans Bethe's Nobel prize-winning model of solar evolution, though it is unclear if Bethe ever knew that the math had been done by one mathematician, rather than her computers. After the war, Blanch was hampered by FBI suspicions that she was secretly a communist. Their evidence for this was nearly nonexistent, and in what must have been a remarkable showdown, this diminutive fifty-year-old mathematician demanded, and won, a hearing to clear her name. She worked productively in numerical mathematics and algorithms for the rest of her life, but remained forever suspicious of digital computers and never adopted them herself.

Grier does excellent research, tracking down surviving computers and sorting through family letters to tell the stories of an entire industry that is being forgotten. He even finds evidence for the working environment for the women computers at Harvard Observatory in the late 1870s in the lyrics to a satire of Gilbert & Sullivan's HMS Pinafore, written by a junior astronomer there at the time.

The book is beautifully printed and has a comprehensive index. Kudos to the Princeton University Press for taking such pride in their work.

When Computers Were Human is weak in several areas. First, Grier glosses over technical aspects of human computing. What were the algorithms that these people used? How was error-checking implemented? He never tells us. Clearly, Grier's goal was to write a work of history, not math, but the people likely to read it are people who care about the math, or about computers, and he omits material that such readers would expect. Second, this is a bureaucratic story. The best human computing was done by large teams sponsored by government in wartime, and the story of these teams revolves around the politicians or bureaucrats who arranged for their funding, and the various acronym-labeled groups that gave them work or provided their employees. At times, it reads as much like a history of agricultural policies as a text about the prehistory of computers.

Grier's story follows his sources: he devotes space to the groups where he has the most material, even if others may have been larger or done more important work. Finally, his discussion of digital computers, where they play a role in the story, is cursory, and may not give credit to those who deserve it.

Is it worth reading? Yes. Consider the reviews of the final tables published by the Bureau of Standards at Amazon.com: In comments as recent as 2004, people who are still using these 50-year-old volumes comment in several languages on which chapters of the books are most useful, where to beware of errors or outdated methods, and on the special emotional role that these volumes play for those who use them, or who needed them in the past. "I probably would never have gotten my Ph.D without this book, and it is a stupendous classic." "Nearly every time you need a mathematical relation or information you will find it on this book." "If you work with mathematical research or numerical computing, you must have this book," and so forth. This praise, and Grier's book, are fine testaments to the world's first computers.

You can purchase When Computers Were Human from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

theodp writes "To commemorate its 10th Anniversary, Amazon.com announced that on July 16th customers will receive a special thank-you - a concert featuring Bob Dylan and Norah Jones. Of course, customers will be squinting at streaming video while Amazon employees actually attend the concert at Seattle's Benaroya Hall, but isn't it the thought that counts?"

getling writes "Looks like Steve Jobs is almost as unhappy about personal details being publicized as he is with Mac secrets. The book publisher Wiley, who is releasing a new unauthorized biography of Jobs has had its entire line of books banned from Apple stores as a result of their unhappiness with the content of the book. Wiley, publisher of the popular Dummies series of books, as well as the Bible series, is quite surprised, due to the fact that they view the book to show Jobs in a largely positive light ..."

blamanj writes "In another case of SciFi becoming reality, you can now star in an animated film as your FutureCast (tm) face-scan is edited into the picture in real-time. John Brunner, in his Hugo-winning novel, Stand on Zanzibar predicted a similar development in television, lampooning people sitting at home while watching travologues of themselves 'on vacation.' Brunner, in addition to being an excellent writer, had some spot-on predictions of a virus-laden Internet in Shockwave Rider. Fortunately, the predictions of his eco-dystopia The Sheep Look Up have not come to pass. Yet."

blamanj writes "In another case of SciFi becoming reality, you can now star in an animated film as your FutureCast (tm) face-scan is edited into the picture in real-time. John Brunner, in his Hugo-winning novel, Stand on Zanzibar predicted a similar development in television, lampooning people sitting at home while watching travologues of themselves 'on vacation.' Brunner, in addition to being an excellent writer, had some spot-on predictions of a virus-laden Internet in Shockwave Rider. Fortunately, the predictions of his eco-dystopia The Sheep Look Up have not come to pass. Yet."

blamanj writes "In another case of SciFi becoming reality, you can now star in an animated film as your FutureCast (tm) face-scan is edited into the picture in real-time. John Brunner, in his Hugo-winning novel, Stand on Zanzibar predicted a similar development in television, lampooning people sitting at home while watching travologues of themselves 'on vacation.' Brunner, in addition to being an excellent writer, had some spot-on predictions of a virus-laden Internet in Shockwave Rider. Fortunately, the predictions of his eco-dystopia The Sheep Look Up have not come to pass. Yet."

Mentifex writes "As reported in the New York Times, Kansas City Star and other news media, Jeff Hawkins (co-author of On Intelligence) and Donna Dubinsky, co-founders of Palm Computing and Handspring, along with Dileep George as the principal engineer, are starting an AI company named Numenta as a follow-up to Hawkins' recent work on visual processing."

plasticmillion writes "Roger McNamee, venture capitalist and author of The New Normal has just posted the third part of a fascinating series on his blog entitled "Video on the Internet". Here are parts one and two. His basic premise is that media companies are trying to treat the internet as a normal distribution channel like broadcast or DVD, but they need to learn that there are new rules to this game if they are to avoid the errors committed by the music industry. The user comments are also a must read, with luminaries like Marc Andreessen chiming in with their insights."

Futurepower(R) asks: "Before he was hired, Steve Jobs of Apple told John Sculley he was a sugar-water salesman, and perhaps should have listened to his own words. Under Chairman and CEO Louis V. Gerstner, Jr, IBM did well, but was that only because the world needs a global computer service company? Was IBM technically advanced during his tenure? In your experience, can managers with little technical knowledge successfully run a technically-oriented company?" What qualities would such a manager need to keep a tech company healthy?

sleeperservice asks: "There are a multitude of books, tools, and educational programs that deal with managing development projects. Whether you subscribe to IBM's Rational Unified Process or maybe SEI's Capability Maturity Model, whether you read Tom DeMarco's Peopleware or possibly Brooks' Mythical Man Month, there's something out there for you. However, most of these deal with projects that have a heavy amount of development, often new development associated with them. What about the folks in Operations? Let's say you need to upgrade your Oracle-based data management system for 1000 non-technical users? Or maybe you need to migrate your enterprise off of Outlook/Exchange and onto an alternative? What pointers are out there that Slashdot readers have used in such situations?"

An Anonymous Reader writes "In a recent presentation and post, Kent Beck (eXtreme Programming, Embrace Change) highlights Open Quality Dashboards as a means to make software development accountable. Many different approaches attempt to reduce the number of issues creeping in all along the development process. Whether a shop abides by the rules of up-front UML design or test-driven development, or a methodology somewhere in between, the ongoing burst of popularity for tools enabling continuous integration and frequent releases shows the need for unit testing to appear earlier in the development process. In this context, quality dashboards could well establish a credible benchmark for software accountability."

Rakkis writes "A new Hitchhiker's Guide to the Galaxy trailer is available on the frontpage of Amazon.com. From IMDb: "The Hitchhiker's Guide to the Galaxy follows the travels of Arthur Dent (Martin Freeman), who is saved from the demolition of the Earth by his pal Ford Prefect (Mos Def). Ford is really an alien doing research for an updated edition of the universe's ultimate travel companion, "The Hitchhiker's Guide to the Galaxy." -- The Hitchhiker's Guide to the Galaxy opens April 29th.""

fm6 writes "NPR has a story up about the first musicians to compose electronic music. In 1947, Louis and Bebe Barron received an early tape recorder as a wedding present. About the same time, Louis Barron became interested in Norbert Wiener's book Cybernetics and its thesis of common elements in living and artificial systems. This led the Barrons to create a new kind of music using electronic circuits and painstakingly edited magnetic tapes. The Barrons music was featured in various avant-garde records and movies, and finally reached a mass audience in the Science Fiction classic Forbidden Planet."

fm6 writes "NPR has a story up about the first musicians to compose electronic music. In 1947, Louis and Bebe Barron received an early tape recorder as a wedding present. About the same time, Louis Barron became interested in Norbert Wiener's book Cybernetics and its thesis of common elements in living and artificial systems. This led the Barrons to create a new kind of music using electronic circuits and painstakingly edited magnetic tapes. The Barrons music was featured in various avant-garde records and movies, and finally reached a mass audience in the Science Fiction classic Forbidden Planet."

SpottedKuh asks: "Perhaps the days of sturdy laser printers are over, or perhaps it is just my bad luck. I've recently been the proud owner of two paperweights: First, an HP LaserJet 1100, which continually misfed papers and smeared toner. After selling that printer, I foolishly purchased a LaserJet 1012, not realizing just how poorly it played with my BSD systems. Naturally, I've learned my lesson about checking LinuxPrinting.org; but, more than that, I'm gun-shy about purchasing yet another printer to replace my current LaserJet. I look at one of my friends who has had a LaserJet 4P for probably around ten years, and it's still going strong. Are the days of such quality gone, or am I just looking in the wrong places?" "Though compatibility with *nix is a must, it is not all that I want. I want a printer that will be sturdy and reliable, with few toner smears and jams. Also, if I'm going to be dropping all this money again, a duplexing printer is a must! I've heard that there are a lot of design problems with the LaserJet 1320, mainly regarding the manual feed mechanism. Maybe the LaserJet 1*** printers just aren't well-built? So I'm thinking of purchasing a LaserJet 2420d; but, I haven't been able to find many reviews of that printer.

Can the Slashdot community provide me with feedback regarding the printers I have mentioned, or any other reliable duplexing laser for in my home office?"

stevejsmith writes "Amazon.com has announced their Amazon Prime service. For $79, you get free two-day shipping on all items, upgradeable to overnight shipping for $3.99 per item. The offer applies to most media (books, DVDs, CDs, etc.) and can be shared among "up to four family members living in the same household." Apparently the only way they will enforce this family-only sharing clause is by mandating that your "family members" know your birthday."

AngusSF writes "OK, slashdotters, , so is this FEE article Antitrust Benefits Consumers? It Just Ain't So! true?" AngusSF quotes from the article: "... as Stan Leibowitz and Steve Margolis have shown in their book, Winners, Losers and Microsoft, in virtually any market that Microsoft has entered (financial software, spreadsheets, etc.), the effect has been a dramatic reduction in prices and an expansion of output and innovation. Software products that do not compete with Microsoft's products fell in price by 12 percent from 1988 to 1995, but by 60 percent where there was competition from Microsoft.", and writes "I'd really like to see some on-line evidence of this. Has Microsoft competition in office suites really cut prices there?"

Georg Tobin writes "LinuxWorld open source editor Kevin Bedell conducts a very interesting interview with Michael Stutz, author of the new Linux Cookbook, 2nd Edition, on the language of the Linux command line, cookbooks, economics, and what applications you absolutely need Windows for."

An anonymous reader writes "IRC is often portrayed by the media as a haven for illegal activity. The author of IRC Hacks set out to find whether or not this was true. His conclusions are quite alarming, suggesting that 99.9% of IRC usage is illegal although he backs up IRC by saying that it is also used for lots of constructive purposes and is used by open source software developers." Update: 01/21 05:17 GMT by P : The author claimed it was merely 99.9% of traffic "to the top 60 channels" that is illegal, not 99.9% of all IRC traffic.

trickofperspective writes "To defray the cost of this year's session, following budget cuts at host school Michigan State University, the famed Clarion Science Fiction and Fantasy Writers' Workshop is holding an online auction of items donated by past alums. Bidding opens January 28th on items such as a signed limited edition of Neil Gaiman's American Gods, a signed, homeade galley of Cory Doctorow's upcoming Someone Comes to Town, Someone Leaves Town, and more."