Nice little browser. My first impression was great. Loads quick, uses less RAM. I say great job for a beta. I also like the UI, very conservative on space so you can see more of the page.
I haven't tried it yet. I'll check it out tomorrow, but some reports I read is that it has a 'Save As" flaw just like Apple's Safari. What should make it interesting is that Mozilla and Google are partners.
I agree it is a good job for a beta, but I can't use it to access key FTP sites I need for work and it has been a bit buggy on some other forums I visit.
I found one bug: If you are playing audio or video in one tab using the Windows Media embedded plugin, the pages you are accessing from the other tab will temporarily freeze the audio playing in the other tab. You'll hear the audio looping as if it was a remix of a song. The audio continues normally when the page in the other tab finishes loading. It happens every time a page is loading. This is strange when you realize that Chrome uses separate processes for each tab. You'd think that since they are separate processes it wouldn't affect performance.
tried it too, and noticed it didn't load certain pages correctly. Like, this one page i frequent has some links on it. The Links on that page don't load as Links. Strange... other than that like people said...seems ok for a BETA
It's not just about Chrome being Beta, it's also about HTML programmers having to update their code to include a new browser. In some cases web pages will check the HTTP header info to see what browser is being used and then load the page in a way best suited for the browser. If it sees an unrecognized browser, it won't know how to react and will load some default stuff, which probably won't be well suited for your browser. See the HTTP_USER_AGENT string at the bottom: RadioRaiders System Check Other times the browsers just read the code differently. When writing the code for my website, I noticed IE seemed to have the best performance. Firefox wasn't bad, but would load the pages in a strange way sometimes if the code I used was old and outdated, while IE would load it just fine (I think I updated all my pages now and they should work OK in FF :O) I like the idea of Opera (ie: stripped down browser) but since they strip it down I guess they take some stuff out, and I have some real problems with it sometimes not loading pages correctly. ...as for Chrome, I don't really care. I'll stick with IE since it's the most used and what HTML programmers base their code around, so performance is pretty much gauranteed. I don't think there's the need for another browser, but on the other hand, I competition isn't bad and having another choice available is a good thing, I guess. HTML programmers are probably not too thrilled about it tho, since it's yet another browser they have to check their code for compatibility with ...and then the whole idea of Google becoming the worlds largest information handler is a little scary, which is another reason I don't want to use Chrome, but that's a topic for another thread I guess.
With IE, maybe compatibility is guaranteed, but not performance. The minute I tried Firefox I was sold. IE is too slow, it takes forever to open and it makes my computers slower for some reason. Chrome is even faster than FF. Since browsing is what I do most of the times it makes sense to use the fastest browser around. Though there are things IE is still necessary since there are plugins that only work in IE. For instance, if you want to watch a movie on Netflix's website that only works in IE. I don't think they have made a plugin for Firefox yet. Also if you work in IT, managing network hardware is often done through the web which often requires a special plugin which only works in IE. That's the only reason IE is still in my computer. Although I found another strange behavior in Chrome. When I login to one of my bank accounts sometimes it won't let me open one of the pages. Once that happens I have to switch to Firefox since it works fine there.
You could be waiting a while. Google's Gmail has been in Beta for 4 years and counting PS- One other interesting thing, is that Chrome is built using Apple's open-source WebKit, so seems to be some kind of relation to Safari...
My default browser is Safari version 3.1.2 and I am on Windows Vista Home Premium SP1. I've been very happy with Safari and on almost all websites I have no issues with using it. When I run in to a website that doesn't work well with Safari I just switch over to IE for the time being, not a big issue. Overall I find Safari for Windows to be a much better browser than IE.
Hi there.... I'm new. I've been using it for about a month, or whenever the first day was that it was available... It is my favorite, and I've used them all, but it does have some bugs, or you might say it is not fully compatible for sites designed to work with IE and Firefox. I can't do some banking and today a lookup feature on a site didn't work. I had to use IE. I think it's clean, intuitive and I particularly like the tabs on top that you can drag around and separate on the screen. I have wide, dual monitors so I really like it that I can drag one tab over and compare what's on it to another tab. You can also look at multiple site pages at the same time. Lot of useful, non kitschy, not bling bling features.
Well I just switched over to using Firefox as my default web browser. I loved Safari for Windows but a website that I use regularly just did a major redesign and it doesn't work quite as well as I would like on Safari. Course I themed Firefox 3 with a UI that makes it look and act like Safari, gotta love Firefox's themes!
I'm still using FireFox 2 since I'm completely attached to Google Browser Sync, which they have discontinued support for (partially due to Chrome). If Chrome gets support for syncing so that I have my bookmarks and cookies on all my computers, then they'll start pulling me over. But I still have a few sites that balk at FF and want IE, so I have IETab (among all my other FF add-ons). As far as testing for all the browsers, I don't think it should be too bad since most browsers are based on IE, Gecko, or WebKit. I think Gecko and WebKit are getting closer to each on rendering and compatibility, so it will still be testing for IE versus everything else.
