![]() |
Google Browser: Chrome
http://googleblog.blogspot.com/2008/...n-browser.html
Google's got a new browser going beta tomorrow; they've (inadvertently, and then deliberately) released a comic to explain it. Salient features from a quick skim:
And yes, it's available tomorrow; no word on what platforms they'll release binaries for, though. It looks at least as interesting as FF3 as far as desktop browsers on tablets go. |
Re: Google Browser: Chrome
Here's to hoping for an n8x0 port :D
|
Re: Google Browser: Chrome
Aargh, after at last TC39 agreed on the future of Javascript (ECMAScript 3.1), another engine enters the scene... Oh well, at least there will be good things in the new browser, apart from the "new" IE7-ish interface.
|
Re: Google Browser: Chrome
Looks too powerful for the tablets.
Super multi process application on a poor little NIT? :( Maybe it will work out though.. |
Re: Google Browser: Chrome
I hope the tablet can run it. Microb is just giving me headaches now when i open multiple windows of it. trying to open two new web pages results in one or both stop and not load.
|
Re: Google Browser: Chrome
They don't have linux support yet... ARM probably even after that.
|
Re: Google Browser: Chrome
And of course, Google will not use this to further gather any data or direct people to their own online services...
... as somebody wrote in an Austrian news forum today: Google is obviously trying hard in becoming the world's most hated company instead of Microsoft. :/ EDIT: Actually, I get the feeling that during the last months Apple became #1 as the world's most hated company, with MS being #2. But this could be a local phenomenon here... Anyway, I certainly agree with it, I don't think MS is all that bad. |
Re: Google Browser: Chrome
Amen to that.
|
Re: Google Browser: Chrome
Or at least propagate text ads :)
|
Re: Google Browser: Chrome
I somehow doubt that the Google browser concept would work well on limited platforms like the NITs. The strength of Google's concept is that every tab is isolated from the rest by running as an own process. On the NIT, however, you don't have that much RAM available, so that it's better to have all tabs running in once process sharing as much resources as possible. That's why Nokia introduced "browserd".
Also, from what I have seen, the Gecko engine is currently a bit faster than Webkit (but let's see what speed improvements Google will achieve with Webkit). But what's definitely interesting for the NITs is Google's new approach of a JavaScript VM with JIT and proper garbage collection. Since it's opensource, I'm sure it won't take long until Firefox gets the same. :) |
Re: Google Browser: Chrome
Quote:
You can also fork it to direct people to yahoo services :) |
Re: Google Browser: Chrome
Quote:
of course, I myself can do it (or use a different browser in the first place), but I doubt that not having my data hurts google in any way. |
Re: Google Browser: Chrome
Quote:
And for those concerned about multi-process vs. multi-thread, think copy-on-write; it's not as big a difference as you might suppose. |
Re: Google Browser: Chrome
Quote:
So how large would the extra overhead really be? I always thought the main disadvantage of using processes vs. threads is in communicating across them, which in this case shouldn't be a major thing as each "tab" would not really need to do much IPC. |
Re: Google Browser: Chrome
Quote:
|
Re: Google Browser: Chrome
I'm a little worried about this "tab sandboxing" thing...Does it mean you can't open two tabs (windows, popups) and control one of them from the other?
|
Re: Google Browser: Chrome
Quote:
|
Re: Google Browser: Chrome
Quote:
Well, there's a lot more investment in switching OSes than browsers, and many do stop using IE; considering that changing settings in a browser is less still, proportionately more would be doing that (i.e. changing default search) if they hated Google as much. |
Re: Google Browser: Chrome
Quote:
These I think could be great for the tablets. With shared libraries and "fork"s COW, I imagine there would not be too much overhead to a lot of processes. |
Re: Google Browser: Chrome
Well, isn't putting each on in its own process and each one having its own interface essentially just running multiple instances, but under one main window?
I spawn multiple copies of links rather than use one process with several windows. Then when I close that "tab" all the memory is reclaimed and I don't have to worry about any cached pages. browserd, I think, is just the opposite. It is one rendering engine with the ability to respawn the main window. Closing the window doesn't even have any effect on the browser. Am I understanding this correctly? |
Re: Google Browser: Chrome
i think browserd is more complex than that.
it seems the window is what holds the current rendered page and data, so that even if browserd dies from a bad script or something else, the different browser windows dont die, except for the one that was connected to whatever it was that made browserd die... but this is me sitting on the fence, observing the process list... |
Re: Google Browser: Chrome
Quote:
http://linux.about.com/od/commands/l/blcmdl2_fork.htm So in theory, if there are very few changes to the pages of a virgin webkit and that there is little in common between once rendering pages, then the overhead of separate processes would be negligible. Disclaimer: I do not know details of browserd. I have no clue what benefits it might have by what structure it might use. |
Re: Google Browser: Chrome
Quote:
|
Re: Google Browser: Chrome
Should be available for download Noon PDT (1900 UTC)!
|
Re: Google Browser: Chrome
The download link is back up at http://gears.google.com/chrome, but the "accept and install" link seems broken.
EDIT: The link at http://www.google.com/chrome now seems to be working OK. |
Re: Google Browser: Chrome
|
Re: Google Browser: Chrome
First itT post on google chrome!
itT runs faster on this I swear. |
Re: Google Browser: Chrome
second post? darn!! fresh from chrome
|
Re: Google Browser: Chrome
Quote:
|
Re: Google Browser: Chrome
Jesus H tapdancing christ this thing is flying
=D |
Re: Google Browser: Chrome
ok if google keeps this thing going this good I will be uninstalling firefox.
|
Re: Google Browser: Chrome
Holy crap, this thing is fast! Wish I could move my bookmarks link to the left, though. Haven't found print preview yet, either.
|
Re: Google Browser: Chrome
First impressions:
1. Faaast! 2. 78/100 on Acid3 Test 3. Tabs work great 4. Bookmarks are easy to maintain and move around 5. Gears is installed by default - works great with Wordpress 6. Haven't seen a site that doesn't render correctly -- even those heavy in Ajax 7. Flash sites run well 8. Silverlight not yet compatible 9. Mobile Me works |
Re: Google Browser: Chrome
Reggie, all that on the IT?
Here is the source code: http://dev.chromium.org/getting-involved I'm not a newbie, but since i never compiled anything, could anyone post instructions of getting it to work? Does it runs faster than Fennec M6? Thank you all. Saludos, Binky |
Re: Google Browser: Chrome
Quote:
Quote:
|
Re: Google Browser: Chrome
Quote:
sjgadsby, really? Are you running it on XP or Vista? |
Re: Google Browser: Chrome
Quote:
EDIT: It's working on another XP machine. One without Parallels. |
Re: Google Browser: Chrome
Quote:
|
Re: Google Browser: Chrome
only thing I havn't been able to do with Chrome so far is access my VNC server over browser with it.
|
Re: Google Browser: Chrome
Quote:
-T. |
All times are GMT. The time now is 01:11. |
vBulletin® Version 3.8.8