This is a perplexing no-brainer error. Afterall, this is the company that has brought us so much, underpinned by writing or rewriting the book on datacenters, storage and databases. I understand that its field testing or in Google-speak "Beta", but "running out of disk space"? +3 for communicating what the issue was and apologizing. -5 for it happening in the first place.

I'm not a coder, but I try to keep up with what's going on. Many replies have sited that libraries are now doing the heavy lifting based on the back breaking and artisan level skill of coders passed. Another reply stated roughly that coding drives chip design and chip design drives coding. This is the key why programmers, while not in great 90's style artificially and foolishly created demand will continue to exist. Intel has scrapped its P4 4Ghz plans and is shifting to the Pentium-M multicore theory. AMD has implemented its AMD64 strategy and Intel is following suit. A program will not take advantage of the full capacity of even the current-day AMD64 chips unless it is recoded to take advantage of those extra advantages - some of those will be realized through recompilation while the majority will be realized by going through the code again. It is stated in many places online that consumer desktop / business workstation applicatons / the predominant Windows operating system are not set up to give a rats arse about whether there is any SMP action going on. This coupled with the benefits of AMD's HyperTransport strategy and (gasp!) Intel's wanting to bring out FB-DIMMs will change how one optimizes an application or how they write it entirely. The programmer lives and will live for some time to come. And please, I've interacted with several thousand users in my lifetime and if they can figure out how to add two cells in Excel they're lucky.