Development, Privacy, and Standards for Chrome
Continuing our coverage of Google Chrome, snydeq points out an Infoworld story about looking at the new browser from a developer's perspective, and another about how WebKit should be the focus of development efforts, rather than the browsers that use it. TGdaily notes that Chrome's search box will fetch all types of data, and can be made to display banking information with little effort. ABC and coderrr have slightly more paranoid articles questioning Google's commitment to privacy. NetworkWorld suggests that Chrome's unique process model (explained here) will require the development of new measurement standards.
Webkit is completely safe; Apple is completely good and noble. Google will maintain complete confidentiality within the marketing department of whatever the browser accessed concerning your confidential business data, bank account details, medical information and personal preferences in pornography. Apple won't even tell you about you.
http://rocknerd.co.uk
If you want to try Chrome, use this version without the silently installed, never removed and hard to disable 'Google Update'.
I felt a great disturbance in the Force, as if millions of voices suddenly cried out in terror as their managers noticed that this Webkit browser has a couple of percentage points.
Yes, it's fast. With a couple of tabs up it also takes up half of my CPU. Browsing three norwegian news sites (ap.no db.no vg.no - all use flash for ads etc.) on my AMD Athlon X2 6000+ uses at least 50% of the CPU and nearly 200 MB of RAM. Try it yourself...
I would love to see Firefox move to WebKit, it would certainly make life easier for web developers.
So google stripped the HTML 5 standard local storage api from Webkit to use their own implementation Google Gears. Why? The api was already there, and it worked, so they had to strip it out to go with google gears, their own, not w3c compliant. I think they are starting to become evil.
I just don't trust anything that bleeds for five days and doesn't die.
Indexing of HTTPS pages is most certainly a bug. Did the poster of the article report it to make Google Chrome a better product or is he just going to complain? It's only in beta.
And the work around is simple: Use Incognito mode for all sensitive work. Which is what it's for.
You realize that the windows don't have to be maximized all the time, right?
http://wiki.winehq.org/Chrome https is not yet supported, but page loading speed isn't bad.
You know the whole problem with IE started when it became the only rendering engine in town?
We all benefit if Webkit, KHTML, Gecko, Presto, and yes, even Trident are upgraded.
From firefox help:
Open in New Window : Shift+Left-click