[enaberif]

Originally Posted by S_G

Renders the same as Safari 3, more or less. You don't have anything extra to hack for. In fact, I have been working on an advanced JS/CSS system for the past couple of months. Chrome not only rendered it flawlessly, but did it in less time.

I'm loving it so far. It's a very early beta, obviously lacking in some areas, UI has issues (eg. a bad SSL problem, where it "looks" like a site does not have SSL if their certificate is invalid but secured). The "skin" is that way, I assume, to maintain OS portability. Hopefully they'll work on this, but it isn't a priority in anyone's book. The developer tools, although preliminary and basic, are AMAZING.

As for the guy complaining about memory, go away. I'm tired of explaining to people that RAM is there to be USED. It's a problem when the browser is using 500MB for 10 tabs of basic web pages. What you shouldbe complaining about is when memory is used inefficiently. Firefox handles memory inefficiently. Windows handles memory (somewhat) inefficiently. Chrome is one of the first pieces of general software that I've seen properly use multithreading (or multiprocessing) and memory.

Excuse me? Nobody was complaining it was simply something I did not like. I don't like seeing my task manager FULL of chrome processes. I'm sure they could thread it so each one is still a process of a main process or something of the nature.