On 8 Jul 2009, at 23:25, Sean Whitton wrote:
Hi,On Wed, Jul 8, 2009 at 15:21, Ezra Morris<epcmorris@xxxxxxxxxxxxxx> wrote:What are people's first reactions to Google Chrome OS? http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html Looks to be quite interesting, although I've never been a huge fan of overly web-based stuff.It's pretty cool how these things work, but I agree with your sentiment. Web based stuff tends to run less well than things designed to actually make use of the hardware you have in front of you, instead of making it little more than input and output for someone else's server running someone else's opinion of how your software should be coded and patched and configured. Wouldn't it be better to teach people how to use their computers properly, make automated backups an easier process perhaps, than to simply say "okay you can't be trusted and you know you can't, we'll run it all for you and you can let your processing power go to waste"?
Depends on the nature of the application. If it's for 'original content creation' - e.g. word/text processing, graphics, music, then I agree. However, for anything that's largely about creating & manipulating large volumes of standard data records (e.g. an HR application) there are strong arguments in favour of using the central server approach - you need to store the data in one location in a single database, for example. Another reason is that there are always upgrades - changes in functionality - to these applications and trying to push changes to code in a bespoke client out to a large nuymber of remote PCs is a challenging task. What has happened is that for these application the browser is becoming the client of choice, talking to a multi-tiered web application with an RDBMS behind it.
Tom Burke _______________________________________________ Sheffield Linux User's Group http://sheflug.org.uk/mailman/listinfo/sheflug_sheflug.org.uk FAQ at: http://www.sheflug.org.uk/mailfaq.html GNU - The Choice of a Complete Generation