Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Google's browser: Google Chrome
It is clean and fast.
It is based on Webkit:
Official Build 1583
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13
http://tools.google.com/chrome/
It is based on Webkit:
Official Build 1583
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13
http://tools.google.com/chrome/
0
This discussion has been closed.
Comments
yes; I'm obsessed with efficiency (in modularity), and web browsers, and many other mostly inane things.
Based on Webkit but way behind Safari3. No CCS3 @font-face, rounded corners are buggy, no text shadow…
I know this is a first release…
Nevertheless I'm glad webkit got such a tender. It's the best web engine so far.
It does eat a lot of RAM, but less than firefox (for me - I'm a heavy tab user) and it keeps running far smoother. Don't forget that it is currently still a beta (that's not an excuse for things, merely a mitigation ). Also, with RAM as cheap as it is, I'm glad to finally start seeing some programs to put it to good use. I don't care if something uses lots of RAM if it performs well, which Chrome does so far for me. I have 4GB, but I know most people don't, however, even cheap new PCs come with 3GB nowadays.
Max_B, I hear you on the older webkit base, but hopefully they will update this to a more recent one before the "final 1.0" product - no reason they shouldn't (is there?). I still prefer it to Safari though. There's just something clunky with Win/Safari that I can't quite put my finger on. It's not a bad browser by any stretch of the imagination, but...
My only fear with Chrome is that it'll go the same way as GoogleTalk did. I remember testing out GoogleTalk when it was launched along side the relatively unheard of Skype a few years back. There wasn't all that much difference between the two then, now it's a completely different ball game. Still, fingers crossed they keep this as an actively developed project.
Another thing I really love about Chrome is the tab management. Being about to pull a tab out of a window to create a new window and then move others to that window is really powerful I find. I can't wait for that behaviour to turn up in fx/saf 4
Stash, you hit on a big point: FF largely is the extensions. I am concerned about speed and memory and ACID3, but the extensions are what keep me loyal to FF. And I am very restrained compared to some of the extension whores out there.
IE and Opera and Safari and Google haven't quite figured that out yet. FF will have to start looking pretty crappy before I give up Flashblock and my other toys. As a developer it totally infuriates me how bad their SVG support is but as a user I'm pretty happy with the day-to-day experience.
Good luck to Google, competition is good and all that. I've just seen too many web browsers as "promising betas". It's relatively easy to make a browser look awesome when it's only 80% finished. That last 20% will kill you every time. That's true for a lot of projects but it's 10x as true for browsers. The web is a tangled mess with a million little corner cases and catching them all is what turns a svelte fast simple browser into a bloated train wreck.
IMO Safari on window is still the ONLY way to test web site against CSS3 features (some mentioned above - dynamic fonts are so cool!), nevertheless, I agree it's slow launch (must load quartz, for font antialiasing and such) and crash often.
I really do hope they update webkit in Chrome soon, it would be superb to have some decent competition in the browser space.
The more I use it, the less I find I miss the extensions in Firefox. That's not to say I wouldn't feel happier with Adblock Plus, NoScript, Firebug, Delicious, Stylish, Greasemonkey, IETab and Gspace What would be really interesting would be if someone wrote a plugin for Chrome that enabled native Firefox extension support...
fx 3.1b1pre — 85 Gecko/20080906062345 Minefield/3.1b1pre
O 9.52 — 84
Chrome 0.2.149.27 — 78 (Official Build 1583 — AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13)
S 3.1.2 — 75
fx 3.0.1 — 71
IE8b1 — 18 (dismal)
Not bad for a beta methinks Chrome also fails the quickest, always useful ! Webkit nightlies aren't working for me...
That was worth a wait LOL
Finding the bookmark and the tab back button history were not that intuitive but is so clean as a result that it is ok.