Why? Well because it's about 80% a test of the underlying system (Ram, CPU, Video card etc) I ran it myself by doing a pretty simple check (removing 75% of the ram going from 2G to .5G) and the performance diff was huge. In short. They spend too much time testing the performance of the Hardware and too little testing the browser against itself.

And my "but" is. they assume (wrongly) that one is always operating on an MS system with all windows maximized at 1600X1280. How many people are there on the ever more popular netbook (1024x600 or 800x480) or don't do the MS max to all dance and actually use multiple cascading windows as god and Xerox Park intended. ;) I HATE be forced to maximize an app just use it. (cough pdf readers cough) and like so many not all my screens are monster LCD desktop systems (in fact notebooks outsell desktops and netbooks lead the portable pack of late.)

Please if any would listen remember these 3 things. 1. Not all or your users are Windows encumbered. 2. Not all of your users are on Desktops with massive screens. 3 Not all of your users like wasting real estate. It won't be long until smartphones are able to do document.... er... wait I already am doing docs on my Android, never mind.

the 30CT a 486DX version was originally only an Asian release. The Libretto50CT was a P1 version running at 150mhz (if memory is correct) This version had sound where the 30ct did not. Size was identical to the size of a vhs cassette case. If anyone out there thinks typing on an early EeePC is hard you had nothing on the Libretto's. Great system, Rock solid, Loved mine.

At a company I left recently I installed Openfire and our supported IM client was their spark client (however despite my ex-bosses rants a lot of clients ended up being used by employee's) Spark works really well. Openfire is rock solid. It runs on Linux or Windows (better on Linux less server load). Without a hitch. Live upgrades work, and if you use mysql as the DB backend you can have auto failover. SSL 3 and TLS are supported as well.

During the 70's we learned that the way things operated in the USSR military was that a brigade commander would be given a map of the local roads, without topographical details and the names of the beginning and ending point of the mission marked on the map. The battalion commander would get a map of the immediate area around the path they were to follow, with the beginning and end points. The company commander would get a line map of the mission with dots not names. The Lieutenant would end up with something like the directions you get from a gas station "Go down this here road to the 3rd left. One of the things they would send back to the Soviet Uninon would be gas station maps of US highways. So my question to the Republican party of California (and this includes you Arnold) Are you Americans or Soviet Socialists afraid of their own shadow and scared to death of knowledge. Frankly I think they are little more than Putin puppets. But that just might be me and me alone.

Whatever you do, prior to the moment you encrypt the first partition, have in place a policy for cryptographic rotation and key retention. The last thing you need is to have one of your key persons leave for greener pastures leaving behind all their data and none of their keys.
In order to be effective the policy for key storage must be one that there is no exception to, period, nada. Changes yes. Exception no. Then figure out a secure way to retain the keys the prohibits rouge usage.
Finally figure out how you will go about a full key change. What happens if Joe leaves in a less than polite manor (he got his butt canned for cause) and this individual may have copies of the keys. How do you rotate, what gets rotated first etc. Cover your butt when it comes to data destruction as well. The more effort you put into planning, the more likely you are to keep all of your data usable.

I want .... really I do....

1. Using Unix (Special Edition 1999) By Steve Moritsugu, Julia Kelly, Steve Moritsugu, without this book I never would have gotten out of the quagmire I first immersed myself in.

2. Linux Shells by Example By Ellie Quigley. Not much missing in this tome. Sed Grep Awk(gawk) bash csh and more.

3. nearly any pocket book by O'Reilly. This is AFAIK all I'll need to keep me going. All the rest are for fun.