Chrome first impressions

First 5-minute impressions:

  1. It has downloaded and installed seamless and quick, importing Firefox configuration.
  2. I have three tabs (start one, Chrome presentation and this blogger one), and 4 processes at the task manager. Total, 95MB. Firefox, with the same tabs, 60MB. They've already said that one tab - one process model would have some startup overcharge. I don't mind if it cleans memory as good as it should.
  3. Vista windows look... but optimized. No right, left or bottom border, and tabs are placed on the title bar, smaller than XP standard ones. Clean UI.
  4. Quick start page displays also last searches.
  5. Flickr Organizr works REALLY fast, and it doesn't make browser stop at all... Javascript is the key and reason of being of Chrome, that's sure...
  6. Moving through tabs isn't fast, it's instantaneous.
  7. Flash works from the very beginning.
Stay tuned :)

Google Chrome: web operative system

You all know a browser has almost nothing in common with the traditional operative system concept, but if applications keep on their current trend of being at web the browser will be our application runtime environment.
This is why Google (is going to) publish Chrome, and they say it in a subtle way at page 4 of the comic: "we're applying the same kind of process isolation you find in modern operative systems".
It also shows some other interesting things:

  • When they build the core a bot test it against "millions of pages". Can you imagine testing against the n most used pages?
  • They've built a Javascript virtual machine which is a JIT compilar which produces machine code.
  • 'Omnibox': the knowledge they've gained with its search box is applied to the URL bar address. Seems terribly simple and useful.
  • Silent mode for being traceless.
  • They critizise Vista security model, which allows reading upwards at the security stack, in spite of having sensible information at the middle of it. Chrome, isn't based at levels but at a sandbox where code can only retrieve information user explicitally gives. They compare Chrome again against a OS instead of a browser.
  • Plugin isolation at a different process.
  • Blacklisting.
  • Development improvements will be integrated at Google Gears. This way other browsers can still benefit Google improvements, and applications can be cross-browser compilant. But, if Chrome has a much bigger throughput, Gears will crawl instead of running on them (IMHO)...
  • At page 36 they state they believe Open Source, not standards (at least not at their 'unifing' function): "Open standards are one way to help all browsers get better. The team has also done some interesting things with speed, stability and the ui, like the new tab page. Some of them might become standards, some might not. But since it's open source other browser developers cant take what they want out of it".
    • IMHO tis is true... in part. If you "unstandar"what browsers do, pages won't behave the same way. Nevertheless, also IMHO, this is the right way of thinking. Standards are slow and burocracy limited.
Let's see what it has to offer... Reading the comic has created a great envy on me. It must be great working at Google pushing the limits of the web instead of struggling with its limitations!