Browser Add-Ons To Enhance Your YouTube Viewing Experience

Controls

YouTube is a much-loved source of entertainment; some might think it’s taking over TV due to the sheer amount and types of entertainment: mini web series, tech and tutorial channels, lyric videos and covers etc. It’s no surprise that some of us can spend hours watching YouTube videos on our subscribed list while others can binge-watch recommended videos for the whole day.

Controls

However, there are minor annoyances with the viewing experience that even these YouTube tricks can’t fix. The common complaints (basically First World Problems) are like the layout being distracting, too much white space, and annoying (or awesome) advertisements that eats into your video-viewing time.

To conquer these problems, I am going to introduce to you the Tube Enhancer Plus for Firefox and YouTube Options for Google Chrome.

Awesome “Hidden” YouTube Settings

Both Tube Enhancer Plus and Youtube Options have some pretty cool features, ideal for the serial YouTuber. With them you can:

1. Remove advertisements – Both can let you skip the ads at the start of the video.

2. Enlarge player size – You can also enlarge the ‘video box’ size so that it fills up the space of your browser window for a closer and clearer view.

3. “Dim the lights” – This feature greys out the areas around the video box. This along with #2 maximizes the real estate of your large, high-resolution monitor.

YouTube Resize

4. Set default viewing quality – If changing the video quality often irks you, then worry no more, you now need not manually change it.

5. Set autoplay settings – You can also set the autoplay settings so videos won’t automatically start playing when you open multiple videos in new tabs.

More From Tube Enhancer Plus (Firefox)

Installing Tube Enhancer Plus gives you a few controls at the bottom of your browser window to download or loop the current video on top of the other features mentioned earlier.

Controls

The coolest feature about this add-on is the ability to watch a video on the Firefox Sidebar. This allows (in)effective multitasking as you can surf the Web while watching all your videos.

YouTube Firefox Sidebar

More From YouTube Options (Chrome)

YouTube Options for Chrome has more customizable features. You can hide elements of YouTube like the comments section, video suggestions, video description, title, header and footer from the settings or its keyboard shortcuts. This gives you a super-clean YouTube player.

YouTube Options

Using the mouse scroll wheel while hovering the mouse cursor above the ‘video box’ lets you change the ‘video box’ size, forward/rewind the video, or change the volume level.

Certain features of YouTube Options can also be used on any embedded videos or on sites like Vimeo, Hulu and DailyMotion.

Safari and Chrome aren’t the new IE6 — chill out!

IE6 and WebKit

Internet Explorer 6 was a plague. Not only was it extremely dominant in the web browser market, but it also highlighted a very dark time for Microsoft as a company. IE6 accomplished Microsoft’s infamous embrace, extend, and extinguish strategy, but it also allowed Microsoft to become stagnant. Since Gecko- (Firefox) and WebKit-based (Chrome, Safari) web browsers have really taken off, Microsoft has quickly moved to rectify the problem. IE9 and IE10 are much faster and more standards-compliant than previous efforts, but Microsoft’s corporate culture taints the way it views the current browser market.

It’s clear that Microsoft sees WebKit as a threat — specifically in the mobile space. Due to its almost complete domination of the smartphone (Android and iPhone) and tablet (Android and iPad) markets, this has even caused some people to accuse WebKit-based browsers of becoming the entrenched, stagnant stalwart that IE6 once was. The reality is that WebKit is not, will not be, and can not be the same problem that IE6 once was. Internet Explorer 6 was part of Microsoft’s plan for dominating the market. Safari and Chrome, despite their importance, don’t serve the same purpose for either Apple or Google.

The reason Apple forked KHTML to start the WebKit project was so that it would no longer be beholden to Microsoft. As stagnant as IE was on Windows, it was even worse on the Mac. Safari, and the underlying rending engine, exist only so that Apple will have a reliable web browser for its customers regardless of which third-party companies are developing for its platforms. Google makes the vast majority of its money from advertising. Its goal is for as many people as possible to use its web apps and services. Chrome exists as clear and stable way for Google to offer a clean and fast experience for its users. In both cases, it doesn’t actually matter if the end user is using a WebKit-based browser. As long as you’re buying Apple’s hardware or using Google’s web apps, neither company cares which browser you use. At least in the days of IE6, Microsoft desperately wanted Internet Explorer to be the only browser anyone ever wanted to use. Google and Apple don’t share that idea for their browsers.

WebKit Browsers

WebKit is completely open source, and anyone can leverage it (or fork it) to create their own browser. Google did it for Chrome, and it turned out fantastically. Microsoft’s Trident engine is closed source. Nobody can fork it or even submit improvements for Microsoft to use itself. This alone means that WebKit cannot really be used as a tool for embrace-extend-extinguish. Extinguishing doesn’t work so well when your competitors have access to the core of your application, and can use it themselves.

The only argument left for WebKit-based browsers being at all like IE6 is that WebKit has features that aren’t yet available in other browsers or in any spec. If web developers want to take advantage of a WebKit-exclusive feature, or if they want to target the vast majority of mobile browsers, they have to write WebKit-specific code. Now, with Firefox and Internet Explorer finally making headway in the mobile market, many developers don’t have the resources to re-write their sites using either new standards or more browser-specific code. This is not by any means a failing of WebKit — it is a failing of the competition and standards body.

Apple and Google both want to implement cutting-edge technology, and the World Wide Web Consortium (W3C) is very slow in adopting standards. That doesn’t mean that WebKit isn’t standards-compliant. In fact, WebKit-based browsers are even more standards compliant than IE10. In reality, this is more of a problem with the W3C. It’s hard to blame developers for wanting to take advantage of the latest technology in WebKit, but they know the risks of using non-standard code. Microsoft shouldn’t be worried about Safari and Chrome playing the role of IE6. Instead, it should double-down on standards compliance, and keep pace with new features in WebKit. If developers can write standards-compliant code that works in every major browser, they’ll do it happily. Don’t drag your feet, Microsoft, and you won’t have to worry about developer support.

Now read: The death of Firefox

Safari and Chrome aren’t the new IE6 — chill out!

IE6 and WebKit

IE6 and WebKit

Internet Explorer 6 was a plague. Not only was it extremely dominant in the web browser market, but it also highlighted a very dark time for Microsoft as a company. IE6 accomplished Microsoft’s infamous embrace, extend, and extinguish strategy, but it also allowed Microsoft to become stagnant. Since Gecko- (Firefox) and WebKit-based (Chrome, Safari) web browsers have really taken off, Microsoft has quickly moved to rectify the problem. IE9 and IE10 are much faster and more standards-compliant than previous efforts, but Microsoft’s corporate culture taints the way it views the current browser market.

It’s clear that Microsoft sees WebKit as a threat — specifically in the mobile space. Due to its almost complete domination of the smartphone (Android and iPhone) and tablet (Android and iPad) markets, this has even caused some people to accuse WebKit-based browsers of becoming the entrenched, stagnant stalwart that IE6 once was. The reality is that WebKit is not, will not be, and can not be the same problem that IE6 once was. Internet Explorer 6 was part of Microsoft’s plan for dominating the market. Safari and Chrome, despite their importance, don’t serve the same purpose for either Apple or Google.

The reason Apple forked KHTML to start the WebKit project was so that it would no longer be beholden to Microsoft. As stagnant as IE was on Windows, it was even worse on the Mac. Safari, and the underlying rending engine, exist only so that Apple will have a reliable web browser for its customers regardless of which third-party companies are developing for its platforms. Google makes the vast majority of its money from advertising. Its goal is for as many people as possible to use its web apps and services. Chrome exists as clear and stable way for Google to offer a clean and fast experience for its users. In both cases, it doesn’t actually matter if the end user is using a WebKit-based browser. As long as you’re buying Apple’s hardware or using Google’s web apps, neither company cares which browser you use. At least in the days of IE6, Microsoft desperately wanted Internet Explorer to be the only browser anyone ever wanted to use. Google and Apple don’t share that idea for their browsers.

WebKit Browsers

WebKit is completely open source, and anyone can leverage it (or fork it) to create their own browser. Google did it for Chrome, and it turned out fantastically. Microsoft’s Trident engine is closed source. Nobody can fork it or even submit improvements for Microsoft to use itself. This alone means that WebKit cannot really be used as a tool for embrace-extend-extinguish. Extinguishing doesn’t work so well when your competitors have access to the core of your application, and can use it themselves.

The only argument left for WebKit-based browsers being at all like IE6 is that WebKit has features that aren’t yet available in other browsers or in any spec. If web developers want to take advantage of a WebKit-exclusive feature, or if they want to target the vast majority of mobile browsers, they have to write WebKit-specific code. Now, with Firefox and Internet Explorer finally making headway in the mobile market, many developers don’t have the resources to re-write their sites using either new standards or more browser-specific code. This is not by any means a failing of WebKit — it is a failing of the competition and standards body.

Apple and Google both want to implement cutting-edge technology, and the World Wide Web Consortium (W3C) is very slow in adopting standards. That doesn’t mean that WebKit isn’t standards-compliant. In fact, WebKit-based browsers are even more standards compliant than IE10. In reality, this is more of a problem with the W3C. It’s hard to blame developers for wanting to take advantage of the latest technology in WebKit, but they know the risks of using non-standard code. Microsoft shouldn’t be worried about Safari and Chrome playing the role of IE6. Instead, it should double-down on standards compliance, and keep pace with new features in WebKit. If developers can write standards-compliant code that works in every major browser, they’ll do it happily. Don’t drag your feet, Microsoft, and you won’t have to worry about developer support.

Now read: The death of Firefox

Safari and Chrome aren’t the new IE6 — chill out!

IE6 and WebKit

Internet Explorer 6 was a plague. Not only was it extremely dominant in the web browser market, but it also highlighted a very dark time for Microsoft as a company. IE6 accomplished Microsoft’s infamous embrace, extend, and extinguish strategy, but it also allowed Microsoft to become stagnant. Since Gecko- (Firefox) and WebKit-based (Chrome, Safari) web browsers have really taken off, Microsoft has quickly moved to rectify the problem. IE9 and IE10 are much faster and more standards-compliant than previous efforts, but Microsoft’s corporate culture taints the way it views the current browser market.

It’s clear that Microsoft sees WebKit as a threat — specifically in the mobile space. Due to its almost complete domination of the smartphone (Android and iPhone) and tablet (Android and iPad) markets, this has even caused some people to accuse WebKit-based browsers of becoming the entrenched, stagnant stalwart that IE6 once was. The reality is that WebKit is not, will not be, and can not be the same problem that IE6 once was. Internet Explorer 6 was part of Microsoft’s plan for dominating the market. Safari and Chrome, despite their importance, don’t serve the same purpose for either Apple or Google.

The reason Apple forked KHTML to start the WebKit project was so that it would no longer be beholden to Microsoft. As stagnant as IE was on Windows, it was even worse on the Mac. Safari, and the underlying rending engine, exist only so that Apple will have a reliable web browser for its customers regardless of which third-party companies are developing for its platforms. Google makes the vast majority of its money from advertising. Its goal is for as many people as possible to use its web apps and services. Chrome exists as clear and stable way for Google to offer a clean and fast experience for its users. In both cases, it doesn’t actually matter if the end user is using a WebKit-based browser. As long as you’re buying Apple’s hardware or using Google’s web apps, neither company cares which browser you use. At least in the days of IE6, Microsoft desperately wanted Internet Explorer to be the only browser anyone ever wanted to use. Google and Apple don’t share that idea for their browsers.

WebKit Browsers

WebKit is completely open source, and anyone can leverage it (or fork it) to create their own browser. Google did it for Chrome, and it turned out fantastically. Microsoft’s Trident engine is closed source. Nobody can fork it or even submit improvements for Microsoft to use itself. This alone means that WebKit cannot really be used as a tool for embrace-extend-extinguish. Extinguishing doesn’t work so well when your competitors have access to the core of your application, and can use it themselves.

The only argument left for WebKit-based browsers being at all like IE6 is that WebKit has features that aren’t yet available in other browsers or in any spec. If web developers want to take advantage of a WebKit-exclusive feature, or if they want to target the vast majority of mobile browsers, they have to write WebKit-specific code. Now, with Firefox and Internet Explorer finally making headway in the mobile market, many developers don’t have the resources to re-write their sites using either new standards or more browser-specific code. This is not by any means a failing of WebKit — it is a failing of the competition and standards body.

Apple and Google both want to implement cutting-edge technology, and the World Wide Web Consortium (W3C) is very slow in adopting standards. That doesn’t mean that WebKit isn’t standards-compliant. In fact, WebKit-based browsers are even more standards compliant than IE10. In reality, this is more of a problem with the W3C. It’s hard to blame developers for wanting to take advantage of the latest technology in WebKit, but they know the risks of using non-standard code. Microsoft shouldn’t be worried about Safari and Chrome playing the role of IE6. Instead, it should double-down on standards compliance, and keep pace with new features in WebKit. If developers can write standards-compliant code that works in every major browser, they’ll do it happily. Don’t drag your feet, Microsoft, and you won’t have to worry about developer support.

Now read: The death of Firefox

Guide to: Installing Firebug in Major Browsers and iOS Devices

Firebug

Firebug is a Firefox add-on with cool tools to inspect web page element, debug and develop web pages. There is however no way you can have these tools on other web browsers apart from Firefox.

Firebug

Development of a similar tool for other browsers may take hard work, but it will be of great help if you could get Firebug to work on other browsers too, considering that everyone has their preferred browsers.

Well, here is where Firebug Lite comes in to solve your needs. Firebug Lite is a simpler version of Firebug but it can be used on IE, Opera, Chrome, Safari, iPad and iPhone while retaining similar options and features.

Installing Firebug Lite on Opera, Safari & Chrome

With Firebug Lite, there isn’t any installation necessary. Written in Java Script, you can bookmark a Firebug Lite link and it will be ready for page inspection. So what you need to do is to simply bookmark the link below (you can also drag the link to your browser’s bookmark bar).

Firebug Lite

If you are using Chrome browser, the bookmark should appear as below, if your bookmark bar is visible.

Firebug Bookmark

That’s it, your Firebug Lite should now work when you need to use it.

Using Firebug Lite on Opera, Safari & Chrome

Now you can use Firebug Lite to inspect practically any web page. For this example, we will use Wikipedia.org.

When the web page is loaded, click on the Firebug Lite bookmark you saved earlier and you will see a consol box appear at the bottom of the web page.

Firebug Consol

If we close up, this is what you will see on the bottom left of the page.

Firebug Consol Closeup

Now you can see the (+) and the (-) at the starting point of many lines. The (+) means there are more lines closed under the one-liner of html, and if you highlight the line, you will see which part of the page it represents.

Highlighted lines

But if you want to make it easier to spot the lines represented by any text, photo, link or any other elements on the web page itself, click on the ‘Inspect’ button.

Inspect

Now you can hover your mouse cursor to any part of the elements available on the web page, and you will see the html line highlighted. This makes it easier for you to do some inspection.

Inspect Highlighted

Installing Firebug Lite on iPad & iPhone

Bookmarklets doesn’t really go well with iPad and iPhone. To have Firebug Lite installed on iPad and iPhone, here’s how:

  1. Bookmark this page on your iPad or iPhone.

    Firebug Bookmark iPad

  2. Rename the bookmark to “Firebug”.

    Firebug Bookmark Rename

  3. Select and copy all the script below.

    javascript:(function(F,i,r,e,b,u,g,L,I,T,E){if(F.getElementById(b))return;E=F[i+'NS']&&F.documentElement.namespaceURI;E=E?F[i+'NS'](E,'script'):F[i]('script');E[r]('id',b);E[r]('src',I+g+T);E[r](b,u);(F[e]('head')[0]||F[e]('body')[0]).appendChild(E);E=new%20Image;E[r]('src',I+L);})(document,'createElement','setAttribute','getElementsByTagName','FirebugLite','4','firebug-lite.js','releases/lite/latest/skin/xp/sprite.png','https://getfirebug.com/','#startOpened');
  4. Go to bookmark option and press “Edit”. Then select “Firebug” bookmark.

    Firebug Bookmark Edit

  5. Remove the original URL and paste the bookmarklet.

    Firebug Bookmark Paste

  6. Choose “Done” on your keyboard.

Now, try to open any website and select “Firebug” bookmark and you’ll see a functioning Firebug at the bottom of your iPad screen.

Firebug Bookmark Paste

Conclusion

Firebug Lite is by far good enough to do quick page inspection. You can view html, css and any script used to build the webpage. Although Chrome has its own Web Developer extension, Firebug Lite does not disappoint by a mile.

Chrome on iOS is sluggish, but at least it syncs

Chrome for iOS - icon

Chrome for iOS - icon

During day two of the Google I/O conference the company moved away from the topics of Google Glass and Android to talk about its Chrome web browser and related web technologies. The Chrome web browser stole the show with the announcement that an iOS version would be available for the iPhone and iPad. There were also smaller reveals, such as the fact that Chromebooks would be sold at Best Buy, but those released much less fanfare than the notion of the speedy Chrome browser on Apple’s mobile hardware.

Chrome on landing in the App Store is a big deal. Unfortunately, Apple has instituted some restrictions that handily prevent mobile Safari from being dethroned

With that said, Chrome on iOS is an interesting development and it does bring several neat features to Apple’s mobile users. The most noticeable benefit is gaining access to Google’s Chrome interface. The user interface features a single text input bar for URL and search entries, and tabs listed above the URL bar (with gesture support for tab switching). The Google browser also includes a private browsing mode — called Incognito — that is much easier to find (and use) versus Safari which hides the feature in the Settings application.

Google's Chrome web browser running on an Apple iPhone.Being Chrome, it is able to access and sync browser bookmarks and saved passwords from Chrome browsers on other systems when logged in with your Google ID. Another new feature allows you to see the websites open on your other Chrome instances — on desktop or other mobile platforms — and open them in the Chrome browser on your iPhone or iPad (or the other way around). Users are also reporting that Chrome is able to open more tabs at a time than Safari, which limits you to 8 open browser tabs.

Although Chrome on iOS has several useful features, in the end it is mostly mobile Safari with a new skin. The back-end and underlying web page rendering code is the same WebKit libraries that Safari uses. You will not find Google’s customized “V8” rendering engine — which the desktop version of the browser uses to improve JavaScript performance. To make matters worse, while Safari is allowed to use Apple’s “Nitro” JavaScript engine to speed up page load times and web application performance, Chrome is prohibited from accessing the Nitro libraries (as are all third party browsers).

This means that Apple’s Safari browser will have a large advantage when it comes to performance. Initial benchmarks comparing performance (JavaScript and page load times) between the two browsers do seem to support that statement — with Safari displaying significantly better benchmark results and, in some cases, slightly decreased page load times. Taking away the tweaked V8 JavaScript engine and Google’s other WebKit touchups is a big disadvantage. Granted, this may be somewhat mitigated by Chrome’s ability to pre-fetch web pages, but it is still not good news for the iOS version.

The other major barrier to Chrome overtaking Safari on iOS is that Apple does not allow the competition to be set as the default browser. Any web links given to you in email, messaging, or other applications will continue to open with the native Safari browser.

Chrome on iOS does start to seem like a fruitless venture (pun intended) when presented with the disadvantages (and once the glamor and allure of a new browser wears off). At the same time, Chrome does have an edge in usability — especially if you use Chrome exclusively on your other systems — and it is a foothold into the Apple customer base. It may not win any performance awards (yet), but it does get the Google Chrome name out there in front of potentially millions of people as an alternative to Safari. It will likely be downloaded by quite a few people (at least 2,980 people have rated it so far), who might then check out Chrome on the desktop, on their MacBook, and so on.

Is Chrome on iOS a “Safari Killer?” Probably not, but it will be a successful product all the same.

Chrome for iOS (App Store)

How to Read .ePub Ebooks on Firefox and Chrome [Quicktip]

ePub Firefox

ePub is an open standard format for ebooks, a format used to publish electronic books, magazines and newspapers. The difference between an ePub format file with a normal doc file is its reflowability to suit the many display dimensions of mobile devices i.e. tablets, smartphones etc. It was created to be flexible with font size and text layout, allowing you to read the same material on any mobile device that you may own.

However, it is not possible to open files with *.ePub extensions on your browsers, even though you can do that with *.pdf and *.doc (opened with Google Docs) files. To open *.ePub formatted files, you need an ebook-reader application like those available on tablets like the iPad, or e-readers like the Kindle or Nook. With more and more publishers switching to producing their ebooks in .ePub versions, you may think that the only way you can keep your reading habits up is to get yourself an e-reader or tablet. Hold that thought.

In this quick tip, we are going to share with you how you can open *.ePub files on your browser with EPUBReader on Firefox and MagicScroll on Chrome. These extensions are made as a minimalist ebook reader that will allow you to browse through ebooks directly from these two browsers.

EPUBReader for Firefox

if you are using Firefox, get to the EPUBReader extension page and click the green button ‘Add to Firefox’ to install EPUBReader.

ePub Firefox

When installation is complete, you will see an additional button appear at the top right corner of your Firefox browser, click the button to launch EPUBReader.

FireFox epub reader

You will then be redirected to your reader page where you will find lots of ebook collections that are available from archive.org and feedbook.com for free.

epub firefox

If you want to download an ebook with an .epub extension from the Internet, EPUBReader will automatically load the ebook for you.

fireforx ebook reader

MagicScroll For Chrome

To start reading ebook from your Chrome browser, go to the MagicScroll extension page and click on ‘Add to Chrome’ to install.

epub chrome

Once installed, you can open a new tab and go to this web address:

MagicScroll.net

When the page is loaded, you will see your ebook library. To add new ebook to your library, click on ‘Add a Book to Your Library’.

magicscroll chrome

Now you will be given options to import the ebook from your computer, or provide the link to an ebook source if you want to add them from the Internet.

chrome add ebook

Once added, all ebooks will be accessible from your library.

chrome ebook library

To read an ebook, click on any available ebook cover from your library.

chrome ebook reader

Using MagicScroll on Chrome makes you feel like you are reading on an e-reader. There are 4 menu buttons available at the top left corner of each book page. They will bring you to the library main page, table of contents, options to change font size and theme colors as well as option to download the ebook locally onto your computer.

Conclusion

With these two extensions for FireFox and Chrome, you can now read ebooks from the convenience of your browsers even when you are offline, and there is no need to get an e-reader or tablet, or install external applications for ebook.

20 Awesome “Battle of the Browsers” Artworks

web browser artworks

There was a time when Internet Explorer defeated Netscape and became the most famous (or most used) Internet browser in the world. Well, you know what happened next, basically IE screwed up, letting righteous Mozilla Firefox take over (easily) as reigning champ. Then, Google Chrome joined the war, became a tough contender and swiftly dethroned Firefox.

web browser artworks
(Image Source: foice)

The war amongst the browsers is so famous that, users, who evidently have their own favorite browser in mind, have translated their thoughts about this epic war of the browsers into artforms. Here, we are showcasing 20 creative (and some amusing) artworks that depict the never-ending battle between the mighty browsers. Note: All of the artworks below do not express or represent any viewpoint or favouritism of any particular Internet browser.

Browseristas. Each browser has its own beautiful aura. Note the use of the colors to represent the browsers. (Image Source: eskimoie)

browseristas

Browser Battle. Only one will walk out the arena! And its the users who will decide the battle result. (Image Source: Konayashi)

browser battle

Browsers’ Battle. Google Chrome basically shocked the world when it slammed into the browser war so suddenly, just like what this artwork is trying to show. (Image Source: NYTimes)

browsers battle

Browser Trio. Long long time ago, there were 3 legendary browser dragons named Firefox, Internet Explorer and Chrome, who fought against each other to bring balance to the online realm. Genuine one, DragonarySilver. (Image Source: DragonarySilver)

browser trio

Browser Wars. Shoze is drawing what I currently see. I was once an Internet Explorer’s fan, you know. (Image Source: shoze)

browser wars

Firefox Fights Internet Explorer. If IE’s icon is as cool as what Derlaine8 drew below, it would have gained back some of its lost users! (Image Source: Derlaine8)

firefox fights internet explorer

Firefox vs Internet Explorer. With the rise of Internet Explorer 10, the winner of the battle is yet to be seen. But let’s not forget Google Chrome. (Image Source: Greg Bakes)

firefox vs internet explorer

Firefox vs Chrome. Painted by foice, this awesome artwork showed the truth – for now it’s really just a war between the firey fox and A.I. Chrome. (Image Source: foice)

firefox vs chrome

Firefox vs Google Chrome. Each has their own advantages, but only the one who focuses the most on users will win! (Image Source: crazyrems)

firefox vs google chrome

Fssss. Cool and expressive! Google Chrome is a ticking timebomb that makes IE look over its shoulders all the time. (Image Source: oneblog)

fssss

IE6 Denial Message. The odd one out. Every web designer knows that IE6 is such a bad boy, but for me IE7 somehow inherited its problematic genes. (Image Source: John Martz)

ie6 denial message

If Browsers Were Guns. Hey, I wonder which gun represents Internet Explorer? (Image Source: 9GAG)

if browsers were guns

If Browsers were Cats with Guns. When all else fails, use cats to deliver your message. (Image Source: Hill Top IT)

if browsers were cats with guns

If Browsers Were Celebrities. I agree with the opinion regarding Chrome, although Chrome’s more like Morgan Freeman to me! (Image Source: Walyou)

if browsers were celebrities

If Browsers Were Superheroes. Firefox is strong, Chrome is fast, don’t you agree? (Image Source: C-Section Comics)

if browsers were superheroes

If Browsers Were Transports. An honest review by CollegeHumor, ’nuff said! (Image Source: CollegeHumor)

if browsers were transports

Internet. This was what every web designer said to me, until Google Chrome joined the race. (Image Source: Haikera-Baiketsu)

internet

Internet Explorer’s 15th Birthday. Am I the only one who thought the HTML 5 gift is little bit sarcastic? (Image Source: Gizmodo)

internet explorer's 15th birthday

Mobile Browser Wars. How about a game of mobile browser wars! Judging by the interface, it should be fun! (Image Source: MobilityWire)

mobile browser wars

Which Web Browser Do You Like. I think I like all browsers then. (Image Source: You-Ta)

which web browser do you like

Reflection

Just like the mobile war between iOS, Android and Windows OS, the browser war would not yield a clear winner for as long as their creators continue to forge improvements for their users. I think this competition is really healthy, as in the end it’s the users who get to enjoy all the benefits. This is also a good lesson for designers and developers, that user-focused features and user experience are what truly matters.

I personally favor Google Chrome for its speed and clean interface! What’s your current favorite browser? Sound off at the comments section below.