Bugs in Chrome, so what?
Chrome colored insects is not what this post is about.
Google, not so long ago, came out with their own version of the Internet browser, called Chrome. It made all the hype necessary with such a product from such a company.
I have covered my initial reaction to Google Chrome in the Chrome bug report. This is my follow up of sorts, not to report more on bugs, but to tell you why it is OK to have bugs.
First, I have not used Chrome for the last one week. I am online essentially through a browser, 4 hours a day on average. That browser is obviously Firefox. I first had Chrome on a smaller machine (128MB RAM), so I figured the slowness (my biggest gripe) was partly due to the smaller RAM (although Firefox was not having that ’slowness’). Then I tested used Google Chrome for more than a week or 10 days on a bigger machine (2GB RAM). The slowness was apparently not there. But there were other things…
First off, I have to say this, I am a Google fan to the core. Apart from offering Google Apps setup as part of my Online Business Package, I use practically all of Google mainstream products. I still do not like that their mainstream products like Gmail are still in beta. But this about Chrome, not Google.
The whole Chrome thing, for obvious reasons, has been overstated. Yes, there have been faults in the roll out of Chrome. The overall architecture does not seem flawed (I don’t say this because I am an expert at software design, although I do possess a degree and I am not afraid to use it. I am hardly your next door geek. I say this because people are usually impressed by Google’s take on the whole Internet package).
The problems that are present in Chrome (and there are a few) are not exactly Google’s fault. Three reasons for the bugs:
- it is a software product
- it is a software product
- it is a software product
Any one remotely related to the software industry will vouch for the fact that all software is never ‘perfectly’ done up. Those days are not gone, because those days were never here. Since the inception of software, the product model of software has been that of trial and adjustment. It is not like your average product, where the companies selling, say shampoos, can not put a product in the marketplace to ‘test’ it. ‘Oh, your eyebrows are falling out, we are sorry. It’s only beta. Here, try shampoo version 1.07.’ These lines don’t cut it for your average product. But in software, this is essentially what happens, and this build-it-on-the-fly happens without exception. And Chrome is no exception.
Bugs such as concerns about security, titles on pages not present and the biggest gripe out there i.e. no extensibility, are all legitimate concerns. There are were problems about flash components being edgy while scrolling (viewing Google’s own Analytics dashboard was not exactly a worthwhile experience in Chrome) Firefox is the ultimate browser that does not has all these problems, Google, especially being Google, ought to have a more solid product out there.
What do you think? Is this OK for Google or should Chrome be revamped rapidly rather than the one update it has received so far?
—
Download Google Chrome | Portable version of Chrome seems to be available as well
