Google Chrome Review: first impressions not good
Filed under: Computers, Software | By: Peter Chubb
Posted on: September 2, 2008 | 77 Comments
Well I have been waiting since yesterday to get my hands on Google Chrome, the search engine giant’s open source web browser. So I downloaded it from Google and then installed the software, and then decided to give Chrome a go. My first impressions are not that good.
So I then opened Google Chrome up and had a little play, and that was when I noticed the first of my problems. Firstly I could not find a button or logo to go back to my homepage, on further investigation it seems that you need to have your toolbar on for the Homepage button to appear.
Then there is the problem with my bookmarks which I imported from Firefox, for some reason I could not get them to show up. No matter what I tried I just could not find my bookmarks.
So what are your first impressions of Google Chrome?
CLICK HERE to keep updated with the latest news, share a comment or problems with products and services. Follow us on twitter or read more google news.
Also, Microsoft Training site doesn’t work with Chrome
speaking of chrome, hmmm nice name! but it das some memory problems such as the part where it tabs the pages you have visited and you click, naturally you expect it to load but i always tells you that page has been transffered to another permanent site( eg the most common sites are yahoo, facebook, hotmail. all these sites have been permanently moved so!!!!!!!). the super tech java script v8 engine that does not have backward compatibility with a lot of these sites.
its though impressive for the first edition lets see what updates they have and to GOOGLE Bring it on
Chrome on 21s
Overall (and for what I’ve used it), very nice job!
Read:Google Chrome Review: First Impressions
http://www.analoga.com.uy/en/articles/google-chrome-review-first-impressions.html
Unfortunately far too much of the scrutany is being placed on Chrome’s interface. It has already been stated several times, but I don’t think fully understood. This is a BETA, meaning it has never been exposed to the trials of the average user. As a result, evaluating it on this level is rather unfair. Looking at it from a design perspective, which is all that it has had a chance to do is be designed; it shows great promise.
First and foremost, we all know its faster. The design of the program had a large part do with this. This is intent is evident in a few features, some obvious, some not so obvious. Best example is the built in task manager that monitors Chrome’s resource usage. What a fantastic feature for those who actually want a faster and more efficient browser. Having a link for more indepth “nerd” stats, also a great touch to an already good idea. The subtle counterpart to this is the multi-proc design. Individual process running independent parts speeds up the loading and the stability of the system (two of the biggest problems with ALL other browsers).
The second major point that very few have noticed (in the correct fashion) is its compatibility. Most reviews are outlining Chrome’s incompatibility with many major web sites and web apps that already exist. In reality, the problem here is that VERY FEW web sites and web apps are compliant with any sort of standard. (Review just about anything from any W3C developer for more info on this problem). The resulting problem is that there is no reliable baseline to develop on that would garauntee the site/app works in “browsers”. Instead everything to date has been made to work in IE, FF, Safari, and other named browsers, all of which MAY or MAY NOT function differently. Asking the new kid on the block to understand the language of all other nations in the UN on his first day again seems somewhat unfair.
This is also why add-ins will not work perfectly on first time through. In addition, this is quite possibly one of the major driving forces behind this browser. With the imminent introduction of CSS2 and Web 2.0 services in general, the need for a standards compliant and dependable browser has arrived. Relying on propriatary methods of doing things cannot be continued. The web has evolved to a level where sites are no longer a presentation of content. It has evolved to a state where content is derived and presentation is styled. These things need to be taken into consideration when designing what will be presented, not who is doing the presenting.
Now, I must agree, there are some UI changes that need to be made. However, in defence of Chrome, it has been very bluntly stated that the approach here simple and incremental development. I’d say they are on a damn good track.
All in all, I’m reminded of a simple mathematical principle:
Two variables in the same equation cannot be solved for at the same time.
This notion holds VERY true for browsers. Our current problems is the sites change (variable #1) and so does the way our browser works with them (variable #2). By implementing standards Google is attempting to turn their browser variable into a (reliable) constant. Something that will undoubtly benefit everyone, and if all goes according to plan; will benefit the web as a whole.
… as a side note, all of these posts about not working with facebook, hotmail, and other major web service providers…. I don’t know what the hell your talking about. I have yet to have any problems with any of these sites with the exception of hotmail asking to upgrade my browser, to which i kindly clicked on the link that said “no thank, continue anyway” and all was fine. Seems like it may be related to a user specific setting on the computer more than anything, i’d be willing to bet it has something to do with a piece of security software somewhere.
Interestingly, the new interface for facebook seems faster in Chrome than the old interface. I haven’t fully test flash, but from what I’ve test after Sept. 3rd, I’ve seen ZERO problems.
One other point to note for fellow developers. Several of the nice thigns that FF has for developers is already there, just not where you’d expect to find it. Right clicking on any page element allows the option to “inspect element”. This provides most of the information that FF’s DOM inspector provided. Extremely useful info for developers.
OK, one weird thing about this browser. It can either be lightspeed or snailspeed.
Chrome’s far too basic for users that are use to advanced feature rich browsers like Opera “straight out of the box” or Firefox with add ons.
You can’t customise or configure Chrome like you can with Firefox or Opera.
As for Chrome’s most frequently visited sites feature…..it’s a poor copy of Opera’s superior Speed Dial feaure.
Chromes 3 size only text resizer is pretty useless, as anyone that is used to Opera’s excellent zoom magnifiyer can testify.
Any good points about Chrome?
Well Chrome is fast but not much faster than Opera’s latest browser version 9.52.
Chrome’s sandboxed tab feature is a plus.
Overall though Chrome in it’s current form can’t match Opera.
Sorry Google : No Sale!
Well while all of your complaints about Google Chrome are valid - they are all fixable with time. You all need to keep in mind that it’s still in BETA, meaning that it’s going to take a while - like it does with any browser, even our favorite; Firefox.
But every problem that you guy’s are having are mostly fixed at this point - except Chrome’s problem with Flash…
So no YouTube for anyone until there is a patch for it!
I’ve read there are also some problems with Javascript at the moment. I’d say it’s even Alpha, not beta: too few features are implemented
Thats all we need, another browser
I’m a little worried by Google’s ability to profile their customers even more now that they will have a complete history of all sites you visit etc.