DeviceGuru writes "LinuxDevices reports that a group of companies today unveiled — and demonstrated products based on — a tiny new PCI Express expansion standard. Although it's somewhat larger than the PCI Express Mini Card, the tiny new 43mm x 65mm FeaturePak card's high density 230-pin edgecard connector provides twice the number of PCI Express and USB 2.0 channels to the host computer, plus 100 lines dedicated to general purpose I/O, of which 34 signal pairs are implemented with enhanced isolation for use in applications such as gigabit Ethernet or high-precision analog I/O. While FeaturePaks will certainly be used in all sorts of embedded devices (medical instruments, test equipment, etc.), the tiny cards could also be used for developing configurable consumer devices, for example to add an embedded firewall/router or security processor to laptop or notebook computers, or for modular functionality in TV set-top-boxes and Internet edge devices." The president of Diamond Systems, which invented the new card, said "Following the FeaturePak initiative's initial launch, we intend to turn the FeaturePak specification, trademark, and logo over to a suitable standards organization so it can become an industry-wide, open-architecture, embedded standard" (but to use the logo you have to join the organization).
kaychoro writes "There may be hope for Duke Nukem Forever (again). 'Jon St. John, better known as the voice of Duke Nukem, said some interesting words during a panel discussion at the Music and Games Festival (MAGFest) that took place January 1 – 4 in Alexandria, Virginia, according to Pixel Enemy. Answering a question from the crowd regarding DNF, St. John said: "... let me go ahead and tell you right now that I'm not allowed to talk about Duke Nukem Forever. No, no, don't be disappointed, read between the lines — why am I not allowed to talk about it?"'"
igrigorik writes "In the short span of just a couple of years, the Ruby VM space has evolved to more than just a handful of choices: MRI, JRuby, IronRuby, MacRuby, Rubinius, MagLev, REE and BlueRuby. Four of these VMs will hit 1.0 status in the upcoming year and will open up entirely new possibilities for the language — Mac apps via MacRuby, Ruby in the browser via Silverlight, object persistence via Smalltalk VM, and so forth. This article takes a detailed look at the past year, the progress of each project, and where the community is heading. It's an exciting time to be a Rubyist."
destinyland writes "Scientists from the University of Chicago and the US Department of Energy have developed the first nanoparticles that seek out and destroy GMB brain cancer cells. Nanoparticles killed up to 80% of the brain cancer cells after just five minutes of exposure to white light, showing the promise of nanomedicine — highly-specific intervention at the molecular scale. Because nanomedicine could repair brain cells or damaged nerve and muscle tissue, the NIH has established eight Nanomedicine Development Centers around the country for their Nanomedicine Roadmap Initiative. Researchers have also used gold nanospheres to search out and 'cook' skin cancer cells with light — 'It's basically like putting a cancer cell in hot water and boiling it to death,' says one researcher. And the NIH Roadmap ultimately predicts 'novel tiny sensors ... that search for, and destroy, infectious agents.'"
The Dell 2007FP is a 20" 4:3 1600x1200 monitor. This is pretty much the only monitor we buy at work.
virusfree tells us about a new algorithm that has been developed that the author claims can sort a linked list up to 10 times faster than MergeSort. "BitFast," a member of the Hash algorithms family, is available in C and C++ under the GPL.
An anonymous reader writes "Matt Dillon has decided to develop a new filesystem from scratch to support DragonFly's clustering, rather than port an existing one. From his post: "There are currently two rough spots in the design. First, how to handle segment overflows in a multi-master environment. Such overflows can occur when the individual masters or slaves have different historical data retention policies. Second, where to store the regeneratable indexes.""