Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Early Screenshots from the Mac Version of Google's Chrome Browser

MacRumors

MacRumors

macrumors bot
Original poster
Apr 12, 2001
68,425
39,261


Google's Mike Pinkerton just posted the first screenshots from the Mac build of Google's Chrome web browser.
This week, everything came together and we can now load web pages in the renderer processes and display them in tabs. Here's a screenshot of the very first time I ran Mac Chromium and loaded a webpage:
Click to expand...
005850-FirstChromePageEver_425.png


He warns there's still a "very very long way to go" and he can't predict a possible date, but it does show some substantial progress on the project.

Google announced Chrome for Windows back in September and stated that they believe they "can add value for users and, at the same time, help drive innovation on the web."

One of the features described for the Windows version has been the isolation of processes within each tab. This means that a misbehaving website can only potentially crash the tab that its running and not the whole browser. Also offered is a screenshot for when this might happen on the Mac version of the browser:


010157-st_425.jpg



Article Link: Early Screenshots from the Mac Version of Google's Chrome Browser
 
Article Link
https://www.macrumors.com/2009/02/13/early-screenshots-from-the-mac-version-of-googles-chrome-browser/
Snap!

You just have to love Google.

I sure hope that's not something that gets removed in the final version. Software is too serious much of the time. It's a web browser, let it have some fun.
 
not a compelling browser on windows and even less so on osx. oh well it is nice to have options.

edit: Don't love google...fear them. They are posturing to be a most evil tech company.
 
On the Windows version type about:internets in the URL field.

Hilarity ensues.

I love it. "Internets" with a 's'

INTERSPACEWEBNETCYBERCOMNETSPAAAACCCEEEE!!!!!!!!!
 
this looks promising. i particularly like the idea of only one tab crashing/closing if the webpage has an error. it will definitely get a chance from me when it comes out.
 
I didn't like chrome when I tried it on windows, so I can't really be bothered. It's pretty stupid anyway that they're so far behind on the osx version.
 
Got very very poor interface. So far Safari is best for me just missing good plugins as it is in firefox. But that just Apple thing, have to control everything:cool:
bad bad apple.../slap
 
I won't use it for the same reason I don't use Safari, lack of decent adblock plugins. For Chrome this will be even worse, who wants to use the browser of an advertisement company?
 
Moof1904 said:
I could not agree more.
Click to expand...

How can they be anymore evil than Apple? At least their products are being produced in the US and they are consistently being rated in the top 5 places to work. Why must every corporation be labelled "evil" once it becomes successful? If you bring up Google tracking your location to advertise, how is this any worse than ABC or NBC selling air time to local businesses based on where you are watching TV? Please give us some objective evidence about how Google is "evil". Please educate us.

On topic, this is fantastic news. I can see Chrome coming to the iPhone too, at some point. Perhaps it is part of the "we won't use multi-touch in Android" agreement?
 
That looks awful.

I hope Safari sees something like that too. I hate losing all my tabs when one locks up my browser.
 
Separate renderer processes? Sounds like they are making life unnecessarily difficult for themselves through an overwrought architecture.

If they went with the Mac application model instead of fighting it, you can open up Interface Builder and put a Webview in a tab without writing a single line of code.
 
If it really says "Aw Snap" when a web page doesn't load properly, I might have to make the switch...
 
SydneyDev said:
Separate renderer processes? Sounds like they are making life unnecessarily difficult for themselves through an overwrought architecture.

If they went with the Mac application model instead of fighting it, you can open up Interface Builder and put a Webview in a tab without writing a single line of code.
Click to expand...
The whole point of the process per tab is that if one tab goes up the swanny, the whole app and any other tabs don't go down with it. They're not trying for the easy way, they're trying for (what they believe to be) the right way.
 
SydneyDev said:
Separate renderer processes? Sounds like they are making life unnecessarily difficult for themselves through an overwrought architecture.

If they went with the Mac application model instead of fighting it, you can open up Interface Builder and put a Webview in a tab without writing a single line of code.
Click to expand...

They must be Windows developers learning to program on a Mac.
 
It shouldn't be taking as long to complete as it is considering the Windows one is already finished and it is a Unix based program so shouldn't be too hard to code for OS X, however this is good news :) Especially with more multicore support in Snow Leopard.
 
Would welcome individual processes for tabs in Safari. I hope Chrome does succeed so other browsers can be forced to push the envelope on innovation.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back