While the the summary is wrong on this subject, I can tell you that, yes, manual optimization is part of our work and can slow down the release of our product. If we told a customer that yes, we will be able to do VGA 30FPS H.264 encode. Code optimization on our custom core is going to take some time and effort. I work in the embedded multimedia field.

I think we're going to be very, very interested in this project.

I was initially skeptical because of your abusive use of "unpatented" all over the place, as if this is solely about patents. You don't provide any clear links here, but 2 clicks away, I found this:

The problem is caused by Vista's internals: There is some code that compares whether the name of the file system type is one of the following: "NTFS", "FAT", "FAT32", "CDFS", "NPFS", "MSFS" or "UDF". If there is a match, it is one of Microsoft's file system types and a lot of code is skipped in the Multiple UNC Provider (MUP) implementation of Vista. If the file system type is a third-party type, for example "Ext2", some code runs in the MUP of Vista that always generates an ERROR_INVALID_PARAMETER error status code due to a bug of Vista.

Bug or on purpose? Who knows.

My first reaction when browsing through the article was disgust about the measure being used. I couldn't see the value of graphs about the number of symbols used by different file-system modules. So vfat doesn't use kprintf, woo-fucking-hoo!

But then, the Hamming distance and hierarchical structure struck a chord. Huh, so NFS, uses a very different set of symbols than, ext3. (ok, this may be biased by NFS using a metric fuckton of external symbols where ext3 uses less), which implies that NFS is pretty different, internally, than ext3.

So now, I agree that such a visualisation, while very abstract from the implementation details, can be pretty useful to have a (very) rough overview of the filesystems and their code structure. And I think we need more abstract overviews like this.

Reminds me of Code Swarm, which creates a movie of commits to a repository.

Dear submitter,

A /. summary is a bit like a main page on a website. Make the organization clear. Don't pile on shortcuts to different parts of the website: the reader risks being discouraged trying to find out how best to get to the important part of your website. Less is better.
I actually clicked on one of the links that appeared to go to the "Expedition" website (based on its similarity to other links, as shown in my browser's statusbar!), then changed the address in the address bar to get to the front page.

You actually didn't include a link to your article's front page, for heaven's sake!

Hope this helps for the next time you write a summary.

Actually, I think we're seeing a bit of a comeback. Hackerspaces are mushrooming around the world. (I like to believe the talk at the 24th Chaos Computer Congress in December 2007, Building a Hacker Space, helped provide impetus to this movement.) I also believe DIY culture is on the rise again, as spearheaded by Make.

So I'd say it's not so much that hacking is dying off rather than being handed over to the new generation, which has its own interests.

I don't think anyone outside the CoS's cultists will take such a comment seriously. All the +5 comments I see here are variants of "Bwahaha! Fool." in discrediting Miscavige's analogy.

However, remember that one way the CoS keeps its claws on its cultists is by appearing to them as a persecuted minority. This /. comment is enlightening.

Hence, I believe this comment rather serves to get his troops to hang tough and together.

Not sure if you're referencing it, but someone already made the link:

Cowboy Bebop / Weird Al Anime Music Video

No.

(long story short: Internet killed newspapers like Gutenberg's press killed Bible monopoly by the Church, newspapers just don't know it yet)

Funny, I learned about the power factor problem of CFLs back when I was in high school, at least 10 years ago.

I thought the problem was solved since then, seeing how CFLs are taking over.

Huh, guess I was wrong, and it was just that the economics had overtaking the "minor technical problems" ...

Slashdotted. Use Coral Cache.

Don't worry, though. On launch day the tools will be mature enough to use, and game vendors will have new ray tracing games that look fabulous on nothing but this.

Huh, that thinking sunk another of Intel's efforts, the Itanium. It was an architecture that required explicitly paralleled code (by the compiler). After sending the first samples to labs and universities and anybody interested in making a compiler for it, they thought everything would be good.

Except the awesome compilers didn't materialize. Itanic sunk.

Do. Not. Expect. Compilers to solve your problems for you. If we could, it would be done by now, and we could make awesome optimizing compilers that would target x86, PowerPC, CUDA, whatever, from that snippet of maintainable high-level code you wrote.

It doesn't exist. Don't wait for it. Toolchains suck and will always suck (relative to what you're expecting).

I never did take Slashdot too seriously, but I guess this feature brings my favorite time-waster fully into Alternate Reality Game territory.

Huh, I wonder what it takes to get the slashdot Amulet of Yendor...