Don't Back Down

Tomorrow night there will be a whole bunch of people gathered in Times Square to watch a fancy lighted ball drop from a tall tower. It will be cramped. It will be cold. It will be late. I can attest to these things because I've been there. It's been a few years, but I'm sure if anything, it's just going to be more cramped and perhaps even more cold. It probably will happen at pretty close to the same time, but since I'm even older, it might seem to be later.

Because of these reasons, and because I have made no plans to go to New York - and it's unlikely that I'll do so in the next 24 hours or so - it's not likely that I'll be there. It is very likely, however, that I will be elsewhere, watching another tradition unfold. This one is a bit closer to home, but that doesn't mean that it is any less interesting.

Read "See You At the Pickle" »

Ever since installing Firefox version 2, I've noticed a steady deterioration in my computer's performance, but I haven't been able to put my finger on it. Since installing the 2.0.0.1 update, it's been even worse. For some reason, I decided to try and figure it out yesterday, and I think I've managed to stumble on the reason. Please note that isn't to say that I've fixed the problem - only that I know the cause.

I typically keep 10-12 tabs open in Firefox. Perhaps I shouldn't, but I do. It's just the way that I use it. I almost constantly keep Firefox running. I just have little reason to close it, and with 1GB of memory, it's usually not a problem. Even when Firefox gets up to a couple hundred MB of memory, it's rarely an issue. If it is, I simply close the window and restart it with the tabs intact. I maybe do this every week or so and life goes on. But still, the performance was getting worse.

Read "Firefox CPU Usage and Google Reader" »