Google launches its browser beta today!
Read about it here!
http://www.google.com/googlebooks/chrome/
Download it here, when it’s released (at least, that’s the most likely location…)!
http://chrome.google.com
Also try: http://google.com/chrome and http://gears.google.com/chrome
My thoughts (copied from another forum):
I’m loving the crap out of it. One semi-serious issue I have is that making each tab its own process seems like taking a step back from what was so exciting about tabs back in the day; no need for a separate process each time you open a page. Of course, you still keep the other good bit about tabs, which is that everything’s in one window, so I don’t know quite how I feel about that. It’ll give the windows task manager hell, though.
The basic memory leak solution is really obvious (when you close something, its memory is cleared… duh, that’s the way it should be), though I admire them for figuring out a way to make multiple processes in the same window (groovy as hell), but all of the other advantages of V8, and sandboxing… wowza.
This brings up another interesting question though: if we’re into compiling JS now, to speed up larger JS apps… what about small ones? Don’t those take longer to run instead? It’s the same issue as the first one, in a way. Big, lots of use, intensive browsing becomes easier. Loading two pages, each with one line of javascript becomes harder, instead.
So yeah. And stuff. I think I’m going to get it, because big intensive browsing is my middle name.