i've been using FinderPop ever since MacOS 8; it's an amazingly useful addition to the Mac OS. The developer is incredibly responsive, considering the fact that FinderPop is free!
I urge everyone to donate!
Be Well!

GeekTool is simply amazing!
I've been using it ever since it first came out!
It still works under Lion, except i can't figure out how to configure existing Geeklets, other than doing it in Snow Leopard, and using the preference files in Lion...
Oh well..
Small price to pay for such a great product
Also, contrary to a report below, GeekTool has a tiny --and stable-- memory footprint, and uses barely as much cpu as Terminal (it really all depends on what you do with it!!!)

Be Well All!
Peter

Ps:
here's the command to get the stats from 'top':
top -F -l1 -n0

If you want to show IP addresses connected to your machine:
netstat -f inet -n | grep '.548 ' | awk '{ print $5 }'

If you want just the Pageouts:
top -l 1 | awk '/VM/ {print "Pageouts: " $9}'

if you want just 'Used' and 'Free' memory:
top -l 1 | awk '/PhysMem/ {print "Used: " $8 " Free: " $10}'

Enjoy!

The Chrome team is so obsessed with being at the forefront of WebKit and HTML5 development, imposing on itself a frantic release cycle, that they completely forgot to make Chrome user-friendly...
The 'Preferences' pages are a joke, no configuration options even for such fundamentals as controlling whether a new tab or window opens behind or in front of the current one, etc...
Users have to sift through hundreds of extensions that sort of, kind of, maybe do something similar to what they're looking for, or they're invited to create their own extensions. Again, this is to control basic features!
Chrome is a developer's platform, but even then, they are so far ahead of everyone else that web developers cannot possibly take advantage of all their bells-and-whistles without having to create 3 different sites: one for Chrome, the other one for the rest (Firefox and IE).
The Chrome team would do better to try to make a browser that caters to more to its users needs, so that it can bring more users into the wonderful world of WebKit (and it really is wonderful)..
Since they insist on having a 'beta' version alongside a release(?) version, they could focus more on the UI for the release version. The whole 'beta' thing is a little funny because, if there is one thing that noone can deny, it's that Chrome is exemplary, even in beta form, in terms of stability.
i really wish Chrome developers would read this; i'd like nothing more than use Chrome as my default browser! i just can't get used to browsing the Google Chrome way, i prefer my way, as i'm sure others prefer theirs...
i hope this helps,
Peter