Introducing the Google Chrome OS
googleblog.blogspot.com
Introducing the Google Chrome OS
1–10 of 180 posts
Re: Introducing the Google Chrome OS
#2> The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel.
Re: Introducing the Google Chrome OS
#3Re: Introducing the Google Chrome OS
#4Re: Introducing the Google Chrome OS
#5Re: Introducing the Google Chrome OS
#6I do hope they prove me wrong. But based on their past performance, I am not holding my breath.
Also: Google, if you're reading this, please at least make the typography render properly in this OS. You've already failed at this with Chrome, which has some of the worst antialiasing I have seen in a browser (surpassed in crappiness only by IE).
Re: Introducing the Google Chrome OS
#7Interesting. The one missing piece--a RAD development environment that's as efficient as Visual Studio is at producing fat clients. The business world will only embrace the webcentric model when it becomes as efficient to code in as .net click-once fat clients. The idea of simple, cheap, rugged hardware is very appealing. But programmer time is the #1 cost--businesses go for easy drag/drop fat client apps. Software w…
I don't think that Google Chrome OS would be suitable for most corporate shops that are generally Microsoft centric (and have been for quite some time). I think this free OS will be geared towards light users that primarily use their computer for surfing the web and checking their email.
Re: Introducing the Google Chrome OS
#8A browser is one thing. But an OS? I have my doubts.
Re: Introducing the Google Chrome OS
#9Key Data Point: > The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel.
Re: Introducing the Google Chrome OS
#10A browser is one thing. But an OS? I have my doubts.
What is Windows? It's that thing, in the background, that lets you run all the applications you want to run.
But what if all your applications were written in Javascript and HTML, and had URLs instead of .exe files? With all the extra power built into Chrome, they could still write to file systems, store data, work offline, do sophisticated graphics and parallel processing -- these are not hypotheticals, this is what Chrome can do right now. We're just beginning to scratch the surface of what an app written from Chrome can do.
Chrome can be an OS, for some value of "OS".