« Chrome Hack - How to change Bookmarklet Favicon Icons!
Google Chrome without Spyware = Iron »

19 Sep 08 Behind Google’s Chrome Intentions and Outcome…

We all want to know what Google is thinking and what their goal is with this Chrome browser.  Personally, I thought Google did a great thing by making it open source.  For god sakes, you can now basically create your own browser based on the Chromium and maybe even add your family album as Google gadgets plugin.  (or whatever)

The same thing can be said of Firefox, of which some companies have took advantage and even made a Web Browser-based SQL database browser called Kirix Strata. (It’s built on the Gecko, the open source engine behind Firefox.  You can find details here.)

By open-sourcing it, Google’s already ahead of the competitions like Microsoft while Mozilla is also open source and has been proving itself in the open-source world for years.

I think in 2-3 years, Google can easily blow the market away from everybody not because Chrome browser is awesome right now, but because it will be 5-10 times more awesome by then.  Knowing the number of people who work on the Google search engine as a mass collaboration of engineers to build a highly scalable search engine system, I think this Browser market is already in their hands as they have proved once before with GoogleMaps overtaking YahooMaps with its itsy bitsy pixel mapping technology. (although Yahoo now has the same technology, their maps are almost identical to Google except StreetView and some other features, which make GoogleMaps better.

We will keep a keen eye on how this all turns out, stay tuuuuned by subscribing to the blog! Tags:, , , , , , , , , , , , , , , , , , , , ,

RSS feed | Trackback URI

Comments »

No comments yet.

Name (required)
E-mail (required - never shown publicly)
URI
Subscribe to comments via email
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.

Related Posts