pouët.net

Google Chrome browser was announced in a comic strip fashion, the comic outlines some features looking to address current browser legacy issues.

lets have an operating system inside an operating system!!

We already do so it may as well be made for it rather than using netscape technology from 1973 and wrapping it in a million hacks.

Well. That was mildly retarded.

actually finishing reading that thing, it seems like a nice idea. but i really wonder how many layers of operating systems we need. each one adding more potential interoperability issues with privileges. or atleast defnitly scaling the complexity of the stuff, they talk alot about benefits from virtual machines but in practical terms its always more stuff to install and update, and things that wont work on this version but do on the other one. confusion the waitress if you ask me :S

Hmm... not sure i see the advantage here. It'll be a little more secure (as everything will be in separate processes.. not sure it's that much of an improvement and it'll probably introduce new exploits..) and perhaps faster (like we'll notice that the page renders 0.03s faster.. but hey it'll look good on benchmarks). It should be more stable, as you'll only get a tab crashing rather than the whole app.. if you're lucky anyway.. but how much of an issue is browser crashing?

But if each tab is keeping its own big chunk of data instead of sharing, surely it'll eat ram like a bastard in a pie shop? This is the big issue with virtualisation.. sure you can run 5 versions of windows and linux on one box, but they're going to want a gig of ram each for reasonable performance, and a cpu for each if they're going to be busy.

thats why god invented quadcore and parallel processing :D

Oh yeah, it's a good thing (i have windows + a linux server running in vmware on this box :) but it eats a ton of resources, so it's not something to use lightly. No point fixing a browser that crashes once a month, only to have it run out of ram and crash twice a week.

i saw that on Twitter :)

I think current generation of desktops with dual cores as a budget option need a multi-threaded browser. And the careful memory management will pay for itself, i regularly have Firefox grow to 800 mb.

emacs is my main operating system :)

oh boy, another browser with its own ideas about web standards :(

:( :(
why do new google technologies tend to suck so much? they're always half-assed not completely throught though ideas releases as a beta and hyped on blogs. even mozilla (god forbid) does it better.

skrebbel: Mozilla has even used "Chrome" for many years themselves :)

the more new ideas, the better for web applications!

How can you dislike something with such a shiny logo!

Anything that could let us throw Firefox and IE into the garbage bin is a good thing.

Since it uses webkit to render pages, it shouldn't be too much hassle. OTOH I'm curious to see their JS engine in action : compatibility and speed wise.

One of the cool features of this browser is the "process manager", to see how much CPU, memory and network each tab/plugin consume. Make that into a graph annoted with the events and callback coming from the tab and we finally have a killer optimization tool.

that logo = pokeball

Somehow, the logo makes me start humming "This was a triumph, I'm making a note here, huge success" :)

gloom, i don't follow. you're saying mozilla has been internally using an unreleased browser developed by google?

amy diamond, link me beautiful

I think gloom refers to this. However, that's not really exclusive to Mozilla either, I can remember some DHTML hack for Internet Explorer back in the days which allowed "chromeless windows", or windows without the window border and toolbar etc. I don't think the "chrome" in "google chrome" means the window chrome though.

i've no clue what you're on about, or that page for that matter. what i got from it is
"you can type 'chrome://' as a protocol and then something called 'chrome' does something, but we're not going to tell you what!'. i'm also really wondering what a "window chrome" is, or a "chromeless window". is it some fancy mac term for "border", maybe?