Edit: This post was created on September 3rd, 2008 (the immediate days after the Chrome browser was announced)
Many thanks for Google implementing this idea to become ChromeOS :)
Google just made a massive move with chrome, and you all think it’s simply just a browser :P
I have adapted my IRC conversation in the Linux Outlaws IRC room on Freenode to suit a fluently reading presentation of my conversation and thought process with personal enlightenment.
1) Each tab is a thread.
2) Operating systems(Linux, Mac, Windows) And desktop environments (Windows Aero, KDE, Gnome, XFCE) use the exact same technology for task and window switching.
3) What do u think happens if I create a Chrome bootstrapper from grub/boot menu?
Answer: An operating system that’s basically like a kiosk, but you CAN use HTML files on your computer instead of fetching them from the network for as fast as possible speed, you could just patch text files and not update entire binary blobs of an application to change or even debug a view or application if it’s all in HTML/Ajax form. ;)
The blogosphere’s fabled “Google OS” roots are being rooted very firmly right now and no-one outside Google seems to even realize this, and seems to only see the book by its cover and release event to which Chrome is only labeled “yet another” Browser.
A You tube presentation of Chrome had developers and project lead’s explain Chrome on launch day: You tube Release Presentation (http://www.youtube.com/watch?v=1d1_ool4r7s)
Simply Imagine your whole desktop was as beautiful as any modern web application, all on your hard drive, written all in HTML/Ajax that simply accesses local data on your computer, HTML/Ajax user interfaces that are EyeOS style: http://eyeos.org/en/ that DOES reside in HTML files, and not all binary data with the fact Chrome’s Open source nature is possible to be cross platform, but still allow core parts be compiled per CPU optimized builds.
The fabled Google OS is ACTUALLY possible now since Chrome runs each tab as a process just like an operating system kernel/desktop environment; even with a Linux core running the chrome browser desktop environment, it’s open source extensible nature and future plug-in back-end would make an entire desktop actually plausible!
I hear you say: yeah but HTML isn’t fast enough !!
My reply: the average Windows user just wants their computer to work, without prevention!
Most people have 1-2 CPU cores, and are used to XP & Vista slowing down their computer and have their desktops be entirely latent and are slow as hell anyways, and even so; Chrome’s tabs are an OS process, which can have 1 process per CPU and spawn THOUSANDS of threads internal of each tab!
Also from the URL bar, you could launch local binary programs from just typing /run CCleaner, or /run XChat; some way that can cause a binary to be executed from the “Omnibar” could let existing apps live inside Chrome as a process spawned and managed by Chrome’s internal runtime.
Bottom line is The AVERAGE and the majority of market share DON’T care about Ajax UI’s or Qt UI’s or GTK UI’s, so long as it works and its usable by the person which equals productivity and efficiency. From a developers standpoint(as I am) are plagued by the choice and porting to other UI toolkits; but HTML and Ajax are W3C standardized and can always make new bindings based on the spec.
The majority of marketshare and people care about eye candy as the result, thus OpenGL+HTML+Speed(V8)=eyecandy/success!
My closing thoughts on this are simple, basically every puzzle piece of this that is needed to create this is a reality and already exists, but the pieces are scattered and not arranged into the full beautiful picture yet.
And thats all for now, if you want to contact me or the people I first told this chain of thought to, check my Google Profile http://www.google.ca/profiles/ultimate.evil page for numerous methods of contact.