21–30 of 180 posts
I'm glad Google has identified a need for something like this, but I don't really trust that Google has the right talent to build an operating system. They have serious problems with user experience and interface design (see: Doug Bowman). The mere idea that they are attempting to encroach on an aspect of experience as large as the operating system is to me somewhat scary. I do hope they prove me wrong. But based on…
Interesting. 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…
Can you clarify your statements a bit more? 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.
Let's hope this also means that a Linux version of Chrome is around the corner.
Let's hope this also means that a Linux version of Chrome is around the corner.
Key Data Point: > The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel.
If their approach to Android is any guide, much of the work will consist of eliminating any GNU or GPL components from the (userspace) runtime environment.
I'm glad Google has identified a need for something like this, but I don't really trust that Google has the right talent to build an operating system. They have serious problems with user experience and interface design (see: Doug Bowman). The mere idea that they are attempting to encroach on an aspect of experience as large as the operating system is to me somewhat scary. I do hope they prove me wrong. But based on…
As I said below ( http://news.ycombinator.com/item?id=693339 ): you've not got what they're thinking of as the OS. The browser is the operating system, and the apps are all web apps. The core of the OS is Linux, but the interface is all browser -- you don't install apps, you just type in their URL. There's hardly any OS UI they need to invent that we haven't already seen as part of Chrome itself.
I am curious to see how they deal with this stuff.
Earlier quoted context omitted.
Can you clarify your statements a bit more? 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.
RAD = rapid application development, the business term for "drag-n-drop GUI builders" that we all know and hate. Not having one for the Web is a valid criticism, but if GWT can handle Swing API input then we DO have one.
It sounds to me like jeffspost is over generalizing and suggesting that Google Chrome OS will only succeed if it's embraced by large corporations. The software hasn't even launched and jeffspost has already figured out it's "one missing piece".
Earlier quoted context omitted.
As I said below ( http://news.ycombinator.com/item?id=693339 ): you've not got what they're thinking of as the OS. The browser is the operating system, and the apps are all web apps. The core of the OS is Linux, but the interface is all browser -- you don't install apps, you just type in their URL. There's hardly any OS UI they need to invent that we haven't already seen as part of Chrome itself.
Not really. You still have to be able to log in, store data, set up parental controls, deal with power management and screen savers and wifi networks, choose desktop backgrounds (assuming they don't force you to use a single tabbed window), choose keyboard/language/sticky keys, define trackpad gestures, accessibility settings, etc... I am curious to see how they deal with this stuff.
At least that is how I'd do it. Just type config:wifi in your location bar to change your wifi settings. Visit config:files to browse your local files, etc. Of course, all of these can be bookmarked by default so the end user can click rather than type.
Chrome already does stuff like this with about:memory, about:network, etc.
http://en.wikipedia.org/wiki/About:_URI_scheme#Google_Chrome...