The Boston Diaries

The ongoing saga of a programmer who doesn't live in Boston, nor does he even like Boston, but yet named his weblog/journal “The Boston Diaries.”

Go figure.

Wednesday, January 09, 2002

Must be a compression of the facts

Yesterday on Slashdot, they had a blurb about Zeosync's claim of a compression scheme that supersedes Claude Shannon's work.

I only mention it here because an associate of mine (who will remain nameless unless otherwise told) not only knows the company, but the company my associate works for has been contracted to actually implement the algorithm, which I've been told is so convoluted that even the scientists at Zeosync are struggling to comprehend. I find that rather amusing (not so my associate, who, being the head programmer, has to most likely write the code).

I've also been told it's not a constant 100:1 compression ratio, but that's the best case you can expect to see.

“… oh, and my fan unit is marginal so I've taken the liberty of ordering a new one … ”

Ethernet inventor Bob Metcalfe estimates that more than 99% of the world's computer capacity is wasted. He points out that modern microprocessors, such as Intel Corp.'s Itanium, engage in speculative execution—in which some values are computed or retrieved before they are needed—while doing other work. He says that principle should be moved to higher levels, to the operating system and to application software.

“What's done at the hardware level is really minuscule compared to what could be done,” says Metcalfe, a partner at Polaris Venture Partners in Waltham, Mass. “This is a very old, deep idea that needs to be pursued much further than it has.” He calls the idea “anticiparallelism.”


Well yes, most computers spend 99% of their time waiting for something to act upon, usually the much slower and totally unpredictable user. It's an intriguing idea, but I'm not giving much hope over the software end of things—programmers are already adding too many features not really used or needed, or are incorrectly assuming which areas of the code need improvement (optimization) and wasting time there. What programmers think the users want are rarely the things the users want, who come up with their own ideas of what they want (gasp!).

But hardware is another story.

Several years ago I worked at a company that wrote a package that ran on a large number of platforms, from desktop units to mainframes and in a backroom they had a Stratus mainframe they were loaned to test their software on. One day a fan unit shows up at the office for the Stratus computer. No one there had any idea who might have ordered the unit and when Stratus was called, the office was informed that the computer had ordered the fan unit, as the one currently installed was going marginal and needed replacement.

Now I find that cool! Okay, so I would want my computer to ask permission before buying itself more memory (especially if it's going to be using my bank card!) but still, that's a good use of anticiparallelism. Having it fetch every article from Slashdot is not. Especially if it retrieves comments at a level of -1.

It's sooooo geeky it's cool!

This is sooooo geeky, it's cool! I want one! I have no idea where I'd put the thing, but man … Wow!

Obligatory Picture

[“I am NOT a number, I am … a Q-CODE!”]

Obligatory Contact Info

Obligatory Feeds

Obligatory Links

Obligatory Miscellaneous

You have my permission to link freely to any entry here. Go ahead, I won't bite. I promise.

The dates are the permanent links to that day's entries (or entry, if there is only one entry). The titles are the permanent links to that entry only. The format for the links are simple: Start with the base link for this site:, then add the date you are interested in, say 2000/08/01, so that would make the final URL:

You can also specify the entire month by leaving off the day portion. You can even select an arbitrary portion of time.

You may also note subtle shading of the links and that's intentional: the “closer” the link is (relative to the page) the “brighter” it appears. It's an experiment in using color shading to denote the distance a link is from here. If you don't notice it, don't worry; it's not all that important.

It is assumed that every brand name, slogan, corporate name, symbol, design element, et cetera mentioned in these pages is a protected and/or trademarked entity, the sole property of its owner(s), and acknowledgement of this status is implied.

Copyright © 1999-2024 by Sean Conner. All Rights Reserved.