Google to launch a new Browser

observations from RSnake:
http://www.darkreading.com/document.asp?doc_id=163001
( some fixed already ?? )

 

And RSnake is an authority? I have never heard of the name.

 

Um..yes..he probably is..
http://www.google.com/search?btnG=Google Search&q=rsnake
Potted bio
http://myappsecurity.blogspot.com/2007/02/reflection-on-rsnake.html

 

i have... he is widely regarded as an authority on web security... he was the one who put on the diminutive XSS worm contest a while back...

 

I'm sorry but that link is written by someone who knows nothing about chrome.

Excuse me for not posting source links (please use google)

BUT

Everything he says is wrong, Chrome was not written in isolation.
Most of the team are WWW, browser and security veterans. Including one of the founders of Firefox.

 

Alot has happened since Sept. 4th at Google Chrome. Being a beta, it's a work in progress, and there has been progress.

 

He's talking about peer-review.
What you should point out is that this is still a beta.

 

How much peer review is needed if your team is made out of the the top coders from allmost all the different browsers?

 

Even top researchers from universities receive extensive peer reviews of their papers. Likewise, it would benefit the developers of Google Chrome if they receive extensive peer reviews from other developers as well.

 

Agree

 

I am going to hold off until that address more of the kinks. I am also getting a little nervous at the surveillance power Google can hold over us now.

 

FYI

Mac version is work in progress and the Linux version appears to not even started.

Interesting read (under the hood of Chrome):
http://www.pcworld.idg.com.au/index.php/id;1913014503;fp;16;fpid;1

 

hello, nickr

for linux, i guess you may be happy to see this.
http://www.codeweavers.com/services/ports/chromium/

 

Google fixes Chrome vulnerabilities - but won't say which :

http://news.cnet.com/8301-1009_3-10035004-83.html

 

Google offers cutting-edge Chrome, FIRST UPDATE :

http://www.download.com/8301-2007_4-10042670-12.html

 

Reading "How to update in Chrome help, it doesn't say anything about downloading the switch so you can get updates. It says they are installed automatically. Is the switch just for techies, and the automatic update for the masses, or what's the real story? I'm not a developer or beta tester, but I want updates when they're available. Thanks in advance.

 

Good News Indeed, thanks Prorootect.
It seems that Its time for me to go back to Chrome and leave Chromium.
Chromium did too many tests recently. and i am tired of manually update everyday.

 

The switch for (less stable) developer updates is intended for developers and testers.
Your version will be updated automatically when a (stable) release is available.

 

Yes Wilbertnl; Twl845, Bensec and everyone,

With Google Chrome, on Chrome Dev Channel, you must download : Chrome Channel Chooser ( 100 Kb ), switch on Dev., click on Update - That's all!
ChromeUpdater.exe automatic start ... a fev seconds - update is OK.! That's all!
Now : I have version : 0.2.152.1 . ATTENTION : ONLY for Developers !!! For all of us : remain on the BETA ... otherwise - big trouble ...

Thanks, PROROOTECT ( Beta )

 

Thanks, it works, except 'checking for updates' in 'About Google Chrome' takes forever with this version.

 

Wilbertnl - Thanks for verifying that for me.

 

Hi everyone
I found that all the builds I downloads today can cause surprisingly heavy cpu loads (build 229?(not sure) -2305) than previous builds, when loading most of the forums I usually visit. please think twice before you update to these builds.
just a notice, in case someone will regret like me =)

 

But why need to UAC enable?? Vista UAC is very annoying .

 

I wonder if you (and/others) have noticed the following problem in these recent builds:
If I maximize the browser, I cannot close it by simply left-clicking on the x in the top right.
I must right-click it and then select close!
This did not happen in earlier builds (such as 2239).

soccerfan

 

I can't reproduce this problem in release 0.2.152.1.
Since the about dialog shows "checking for updates" forever, I can't see which build I run.