When I read the publications upon the latest version Internet Explorer, I wasn’t too excited. Through my experience using IE, the browser tends to ‘freeze’ when loading several different tabs. And from the review I’ve read, IE8 is not better compared to the previous versions.
For the last month, I’ve been using a new browser called Flock!. The browser uses Firefox engine, which is available as an open project thus allowing anyone building their own browser. As a result, Flock! is just a modification of Firefox with several unimportant additions. However, since Flock! is way much faster than IE, I use it neverthless.
But then come the new browser, Google Chrome. As Firefox, Google developed Chrome as an open source project. But unlike Firefox, Chrome was built under an entirely new engine developed by Google teams who have so far delivered you cutting-edge applications such as Google Earth and Google Map. After reading Chrome’s presentation, eloquently delivered in a form of comic strips as to help you who don’t speak computer terms, I decided to give it a try. And it turned out satisfactory. I opened Facebook, Yahoo Mail, Friendster, and You Tube all in one window. Those pages are loaded with images, plug-ins, flash videos and all bandwith guzzling snippets. The result: no more window freezing.
Tabs Management
Today’s browsers are enabled with multi-tab capability, so users can browse several websites under a single window. To simplify, let’s imagine browser as a bank teller and tabs containing web pages as bank clients. Under IE and Firefox, what happen is that a single bank teller handling multiple clients. If one client has a problem in his transaction, the other clients must wait until the teller clears the problem. That is why when using IE, Firefox, or Flock!, the browser sometimes ‘freeze’ for a second, or a minute for those who are unfortunate, before you are able to navigate from one tab to another.
Chrome takes an entirely different approach. Instead of providing just one teller for multiple clients, Chrome provides one teller for one client. Everytime a client shows up at the door, a new teller is summoned from the back end office and provide the service for the client. Hence, if one client has a problem, other clients will not endure the effect of queuing, but continue to process his transaction. The ‘freezing’ phenomena can be shortened to a split second or even eliminated. Of course this will burden the computer CPU in the end, but that’s your problem, not Google’s problem. If you lack in computing power, purchase another block of memory.
Garbage Collections
Now this is where most of you will get lost, I guess. Arriving back at teller-client example, this time we will add another object: teller’s desk. Teller’s desk is like your CPU. It holds everything from calculator, screens, pens, printers, and all objects required by teller to complete bank’s service. It is true that Chrome summons a brand-new teller for each client. But the desks remain the same. Now, after completing a client’s transaction, the teller will have a document as proof of client’s transaction, let’s say withdrawal of transfer slip. The more clients the bank serve in a day, the more documents will piled up on tellers’ desks.
These documents will add burden for the teller because eventually the desk will be covered up by documents, all scattered in different areas. Some documents might be stored inside the drawer, some will be left stranded on the desk. Any teller who takes a desk that is already scattered with documents might need some time to rearrange the documents so that she will be able to process the next client’s transaction. And what’s worse is that these documents are hardly destroyed. It’s just possible that a document dated from 2005 is still left stranded on the desk.
Chrome, unlike anyone, hired a top end garbage man. The garbage man will move from one desk to another searching for inactive documents which no longer needed by the next teller. The garbage man himself doesn’t care who the teller is, who the client is, or what kind of transaction the client is doing. He only cares for one thing: once the client finished his transaction, the next teller won’t need the documents any more. Once he spotted a desk which is no longer occupied by a teller, he will take away any documents left on the desk or inside the drawer.
IE, Firefox, and Flock! are all multi-tabbed browser, all lacking a competent garbage man. The reality is, when you close a tab in Firefox, the memory used by CPU to operate the tab is not emptied. Hence, every time you summon a new tab, another memory block is used. The more tabs you open and close, the more memory you use.
Of course, eventually Firefox will clean up unused memories, but most of the time it is too late. Try to imagine hiring a part time garbage man. The poor guy will have no idea which documents are obsolete and which are needed. Since he’s too afraid to dump anything, the only documents he’ll dump are old newspapers. Doesn’t help much, does it?
Try It !
I have no affiliation with Google, nor with any parties related to Google. But if you grown tired with your old browser, it is time for you to try Google Chrome. I’m done with IE. “Everytime the browser tells me to updgrade my browser version, my surfing experience goes straight down the hill !” - The Born Loser, Jakarta Post.