Andy Prough writes: Former Google engineer Jeff Nelson has written a fascinating blog post about how he created "Google OS", the forerunner to Chrome OS. Last August, he finally received a patent for it, but his work began in 2006, and the first versions of the OS were built on Firefox and a "bare-bones Linux distribution" that could execute any Linux program. In fact, when he first started writing the OS, Chrome itself did not exist, and the whole purpose for his work was to create a system that loaded fully — and only — into system RAM. This purpose grew out of his frustration with wait times as he wrote webapps for Google, and found himself waiting 30-45 seconds just to restart a web browser. By moving the entire OS to RAM, he was able to cut the Firefox restart time from 45 seconds to 1 second, and found similar speed increases for other mundane tasks. He built himself a "Chromebook" and used it as his primary development box for over a year. The fact that his boss and Google management originally had no interest in his project makes this story all the better. This blog post is a very interesting read, as it discusses the beginnings of the range of Google webapps that were ultimately created to "replace any and all functionality normally found on a desktop".
Real Programs don't use shared text. Otherwise, how can they use functions
for scratch space after they are finished calling them?