The Browser Wars
June 22nd, 2006First there was Netscape. What would we have done without it?
Then Explorer. What would we have done without it?
Then all kind of strange birds.
Then FireFox came. Truthfully - we did fine without it. But for some of us, we did even better with it
Firefox is great… for most things. It doesn’t support ActiveX (so not good for my bank account’s access. It keeps crashing on me from time to time for no apparent reason. But then again, it supports tabs which I couldn’t do without now. And very nifty plugin system which some are my best buddies now.
As an internet user, you don’t really mind that there are so many browsers. Explorer, Firefox, Netscape, Opera, Safari… there are more… Not to mention the many versions of each of those.
But as a web developer, it’s annoying. Very annoying. At least if you care about your web application working on all browsers. Each browser you use shows the web pages a bit differently. And if those pages are content-rich and full of dynamic and Javascript content… most of the time you will be happy if they work at all
Let me clarify one issue. There is the application which you call the browser, and the rendering engine, which you should call that, or ‘browser engine’.
We don’t need more browser engines. We need browser engines consolidation. Or better yet, more standardization. If only developers adhere to W3C. But they don’t. Mainly because W3C responds a bit too slowly to “real” world needs/demands. If only browser applications would be on a separate level than the browser engines, you could write a browser application using whatever engine you want (which is almost true now), but still there are too many (more than two) engines.
I was reminded about it when I met Netanel Jacobsson from Maxthon.
My first reaction when hearing of the existence of Maxthon browser was “Oh no! not another one”. I was wrong though. Well, starting from the fact that I was technically wrong to classify Maxathon as a browser engine. It’s not. It’s a browser application.
So what exactly is Maxthon? Maxthon is a browser application. You can use it to surf the web. Like you do with Explorer of Firefox (or Safari or whatever)
However, it doesn’t have its own browser engine. It uses Microsoft’s Internet Explorer engine.
Why is that good? Why do we need another web application?
Some of us don’t. I personally don’t. I am happy with Firefox (most of the time). But I am installing patches, plugins and extentions to it all the time. If you know what the heck I just said now, you might be able to do with Firefox. Why not Explorer? Cause it sucks. It doesn’t have tabs, so no need to list more of it’s disadvantages..
Most people on the web don’t want to install anything. To some, even installing Maxthon will be one operation too much. That is why Explorer is popular. It’s there. You don’t need to install it. That is why it’s surprising to hear about new browser applications making it to the public awareness.
Firefox, with its entire geekbase, reaches at most 15% of the web audience. It IS impressive. But also shows the problem. You need to be tech savvy to really enjoy Firefox.
So what if you are not? Maxthon might be just for you. Why? Cause it comes with all the bells and whistles that most people can think of. Tabs, RSS reader.. you name it – it has it. Sometimes too much, but it follows the philosophy of “don’t need it? Don’t touch it”. Which is good enough for most people. It even allows you to use Firefox browser engine instead of Explorer if you really insist
(although why would you?)
Problems Maxthon facing? Some may be simply classified as challenges though.
1. Maxthon is based in China. This is where it was originally developed. It is trying to make it out to the US and EU. Why? I am not entirely sure, since China is such a lucrative market now and everyone is trying to get into it. But Maxthon doesn’t want to get out, only expand out. Fair enough. But that’s not easy. Time will tell how much they are successful in that.
2. Maxthon is undergoing a complete rewrite. If you ask me, that is a brilliant idea. Every product in the world is better off being rewritten every 2 years. Reason is – developers suck at predicting how things should be done 3 years ahead
go figure. Now.. that IS a challenge. But as far as I know, version 2 is almost ready. To my understanding, some of the features that I didn’t like the way in which they were done, are new and improved. I am waiting for the beta.
3. Maxthon is facing the release of the new version of Explorer. This one has tabs. I personally think tabs, once you get to be friends with them, are a killer application. However, Microsoft can not do everything. And they don’t. They do the most needed. But it’s not ALL that is needed. More clearly, Explorer doesn’t support plugins like Firefox does. So if you don’t have it built in, forget about it. That is where Maxthon lives.
4. Challenges I didn’t think of. (I always like to state that the last thing I have to say is that maybe I didn’t say it all)
In the area between what Microsoft does, and what people need. And it’s apparent, there is a big gap there.