Google Chrome
Sep. 2nd, 2008 10:47 amThere's something that no one is mentioning with reference to Google's new web browser. Which is that if you read what the comic says about the browser, that's not a web browser, it's an operating system.
It has a programming language (Javascript). It has a filesystem/database (Google Gears). It has process management. It has window management and display logic. It has permissions-based security. This is not Google trying to compete with Internet Explorer, it's Google trying to compete with Windows -- or rather, make Windows irrelevant.
It has a programming language (Javascript). It has a filesystem/database (Google Gears). It has process management. It has window management and display logic. It has permissions-based security. This is not Google trying to compete with Internet Explorer, it's Google trying to compete with Windows -- or rather, make Windows irrelevant.
(no subject)
Date: 2008-09-02 01:33 pm (UTC)If I need Windows to run Chrome, I'm not really competing with Windows.
(no subject)
Date: 2008-09-02 01:43 pm (UTC)If Chrome does what it should, and your apps move into the cloud, then the OS will be in the same position as the BIOS is today -- you've got to have one, but you don't care which one you have, so you might as well have the cheapest one.
(no subject)
Date: 2008-09-02 04:11 pm (UTC)(no subject)
Date: 2008-09-03 08:15 am (UTC)They'll be competing with Windows when OpenOffice (or equivalent) runs inside the browser. Oh, and World of Warcraft.
(no subject)
Date: 2008-09-03 08:23 am (UTC)One programming language may or may not be enough, but it's all you get on a Windows PC. The language, of course, is x86 or x64 machine code. Anything you write in any other language gets compiled to machine code. Google have software right now to compile Java code to Javascript, and there's no particular reason why the same couldn't be done for other high-level languages.
(no subject)
Date: 2008-09-03 09:11 am (UTC)It'd be nice to have other high level languages compiling to JavaScript - but I'm not sure how efficient, in general, that double-compilation step will be. Compiling down to the new VM would be more efficient, but then you'd be constrained to only Google's browser.
And unless Google get massive traction for Chrome (like over 90%) it won't matter, as you won't be able to rely on people using it as their browser - you'll still have to deal with IE, Opera, Firefox, etc.
(no subject)
Date: 2008-09-04 08:02 am (UTC)And a compiler for Javascript to machine code (p. 15 of the comic), though how many platforms that will eventually work for I don't know. x86 would be enough for many people, but if it's going to be on Android, they might do iPhone and/or Windows Mobile too.
But Googling, it appears that the current Android Java VM (Dalvik) has no JIT compiler, so maybe Javascript won't either.
(no subject)
Date: 2008-09-04 03:21 pm (UTC)http://www.theregister.co.uk/2008/09/04/chrome_review/ starts "This is not just a browser: it is a vehicle for delivering web applications", and compares with Adobe AIR