(I think even IE puts favicons in tabs now.) I suppose it would interfere with the nice clean look of Safari, but it is useful to know at a glance what’s in each tab. This is not unique to Chrome if anything Safari is the weird case here. And not having the close button on the left, as is standard on Mac OS X, didn’t bother me as much as I thought it would.įavicons in tabs. Rather than try to explain this, I’m just going to refer you to an article that explains the intelligent behavior of tabs in Chrome. Chrome handles Flash better, too.Ĭlosing tabs. But leaving Safari open for hours results in it ballooning to a few hundred megabytes of RAM, while Chrome reclaims things better when tabs are closed. Safari is a memory hog, although part of that is running it in 64-bit mode and Chrome in 32-bit mode. (This could be considered a feature, but it’s not Mac-like.) Labels are bolded, the last section has a scroll bar for just plain-old interface items, and buttons that bring up more info open a new window instead of a sheet. But more than that, Chrome’s preferences window just feels wrong. Chrome’s actual preferences may be more customizable than Safari, but you’d have to dig into the low-level settings interface to see that. I’m torn, but ultimately I think I like the classic way better, even if it does take up more space. And I’ve found I really like being able to double-click an empty part of the tab bar to make a new tab, but double-clicking a window’s title bar minimizes it, and Chrome is no exception. It makes sense, actually, to have the tabs above the address bar, but while it does look cleaner with more browsing room, it’s just harder to drag the window around. It’s ironic that the browser is called “Chrome” when one of the original stated goals is to remove the “chrome” (browser interface elements) from your web browsing experience. This comparison comes after using Chrome for a week, then switching back and using Safari for, well, most of a week. (Firefox’s Gecko engine is also pretty good, though.) In the last year, Chrome’s market share has surpassed Safari’s. Like Safari, it’s based on the WebKit rendering engine, so it handles cutting-edge HTML5ed-up websites well. The “feels like a real Mac app” kept me from switching to Firefox, though-the various attempts at faking Mac behavior made Firefox feel like a crippled application, despite any web browsing capabilities.Ĭhrome, on the other hand, is the newest major contender to the browser market (just over two years old), and I’d only tried it for a little bit a year ago. The one thing Safari didn’t have until recently is extensions, and Safari’s extensions are still rather limited (both in capability and quantity) compared to Chrome’s or Firefox’s. (This last is precisely the reason why Safari on Windows sucks, or at least used to suck: it still feels like a Mac app, which is the wrong thing to do on a Windows system.) And it feels like a Mac app, and integrates quite well with the rest of the system. I like it because it has very strong support for HTML5 and various experimental-y features of the web, and because it has a pretty solid and well-thought-out user interface. Safari is the browser made by Apple, and the default browser on Mac OS X. The point of one of these things is, of course, to get more people to try using Chrome knowing full well that that was the case, I decided to use Chrome for a week, and see how it stacks up to my regular browser, Safari.įirst, a note on why I use Safari. The system was easily game-able, since it didn’t test whether you actually used the tabs, but it was limited to million anyway, so Google was pretty much guaranteed to hit it. Last week Google ran a program called Chrome for a Cause, in which Google donated money to charities based on how many tabs people opened in Chrome. It’s still pretty much how I feel about Chrome. This was originally posted on my personal blog in December 2010.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |