February 8th, 2005


the series of badger, part 1

I'm not quite sure how this series started. Obviously it started with badger. And then I posted more badgers . . . and then, a lot more badgers.

The phrase "a lot more" doesn't have much meaning, in fact, compared to how many badgers I posted.

I realized early on that I didn't want a sensible progression. I didn't want anybody, at any point, to say "Oh, that's not much more badgers than the last time!" and I think I succeeded admirably. Every entry has an absurdly large amount of badgers compared to the last entry.

But I'm getting ahead of myself.

The first entry was, simply, badger.

One lone badger.

Don't worry. This is the only entry that can be explained without calculus or number theory. We'll be getting a lot more badgers soon.

(no subject)

Google just launched Google Maps.

Do you have any *idea* how long I've been waiting for that to be public? I mean, sure, at work I'd use it, and then I'd want to print out a map and I'd have to go use Yahoo Maps in case someone else saw it lying around in my car.


At least it's finally out now.

(Go try it. It's fun!)

(no subject)

Apparently Sun Microsystems has decided to go into the CPU farm business. They've got a farm of 10,000 computers and they're selling CPU time for $1/hr/cpu. And they've got a billboard on 101 north, which I drive past every day going home.

And it bugs the hell out of me, for one reason:

What the hell does $1/hr/cpu mean? Do they have ten thousand Intel 8088s decked out with 64kb RAM each, and hundreds of trained gerbils dragging little punched cards back and forth for networking?

Or do they have a farm of prototype 6ghz G5s, each one with 32gb of L1 cache and 10gb fiber, and some crazy ten-thousand-port switch with a hundred-terabit backplane?

$1/hr/cpu. Jesus. That's as bad as describing car engines based solely on how heavy they are.