Google Chromium for Chrome Browser

A few months ago, Google released their browser and called it Chrome. Like most new things established (or acquired) by Google, it has been scrutinized inside and out by tech bloggers.

Although it did not have any record breaking downloads, it did have a good following especially those that are faithful for Google. Of course, one of the distinguishing features of Chrome is that the services of Google will run faster.

If you have tried running Chrome, you will notice that it is lightning fast...really fast when you are trying to run Google's services such as Gmail, Blogger, Google News or Google Talk.

But there is something lacking from Chrome - customization. If there is any company who could offer their users a free hand on everything they want to do, it should be Google.

After all, Google became popular because of their ability to offer customization while ensuring the efficiency of their online application.

Fortunately, Google heeded the call. Just last week, Google released the document outlying the features and functions of the plug-in platform for their browser. They called it Chromium which signifies its compatibility with the browser.

Although no one has said anything about the actual release of the Chromium, the documentation should give everyone a good idea what the upcoming platform for plug-in would be like.

The initial reaction for Chromium is favorable. Google has stayed on what they do the most for their customers. They admitted that they everyone needs something different and there could never be a universal plug-in for Chromium.

Which is why Google needs the help of developers worldwide. They may be able to build plug-ins for general services but as already stated, these plug-ins will never appeal to everyone. The experience is always personalized.

What is interesting is that the documentation of Chromium warns their developers early on. There is always temptation for developers to overdo the plug-in since Chromium is a lightweight browser and almost anything could be added.

Chromium has reminded their developers not to overdo it or else the plug-in will ultimately defeat its purpose.

The plug-in should help developers improve the experience in their browser and it should be in no way to become the main application. Chromium is a platform for plug-ins but it should only be used to aid the browser.

So where does Ajax come into this situation?

Two scenarios:

First and the most probably scenario where Ajax will be most likely added is when the application or the website lack any Ajax based application.

Through plug-ins developers will be able to enhance the interactivity of the application without changing the original interface. Through plug-ins users will have the option in using Ajax.

The second scenario is an add-on to the already powerful Ajax based online applications. Through the aid of plug-ins, Chrome is hoping to improve its services to user which will also increase the popularity of the browser.

It would take time before Chromium could be fully implemented but the documentation should point us to a powerful browser through their plug-in.