Napster and Best Buy Joining Forces
Ruds writes "Best Buy will market a music service co-branded with Napster. Napster will give Best Buy stock valued up to $10 million, and they'll share marketing costs. From the story: 'The retail chain will feature Napster products in its brick-and-mortar stores and demonstrate the service through interactive kiosks throughout the nation. Napster will also support Best Buy's artist promotions.'"
I don't know what you people are talking about... I work at Best Buy (and another place) and I haven't had a decent nap in soooo long. I'm tired now. Time to go to sleep so i can wake up and go to work in the morning
From 0 to drunk in $20
Chief O'Hara: Our lady's tits, Commisioner Ashcroft! That no-good Napster is up to its ol' shenanigans again!
Commisioner Ashcroft: This can only be a job for HATCHMAN .
Google confirms: Ruby is the world's most beloved programm
While reading your comment I suspected that it was done with Speech-to-Text software and a microphone. With a really fast CPU and a well-trained set of individual voice parameters you can get text like this: long rambling and folksy but with almost no misspelled words.
You gotta remember to say "New Paragraph" every once in a while! It's not natural but it vastly improves the readability of the generated text.
This technique is great for commenting source code. Just get the person who wrote it (usually the only person who understands how it works and usually the person the least interested in actually writing comments) to describe what it does by talking about it. Put a picture of a beautiful movie star next to the screen so he can pretend that he is describing it to her (this technique works best with geeky guys) and she is really interested.
After an hour you have an astonishing amount of text that describes in great detail how the code works. Get a software assistant or intern to either edit the comments into the source or provide an HTML link to the correct part of the source from the text description file.
Personally I think source code should look like a thriller novel. The comments should be descriptive paragraphs and the actual code to be compiled would be like dialog with quotation marks around each line. It would be much easier to read after it was finished for its upkeep. It would also be a big advance in software engineering. However, no one else on Slashdot seems to think so.