Browser 2.0

Comments
Forward
Trackback
AddThis

Ok, I'm sure most of you have heard of web browsers, like Internet Explorer, Firefox, Safari, Webkit, and various others. I'm also pretty sure that most people arn't aware that the browser market drives the Web 2.0 market. This is caused by a few things, which I'll get into, in a moment.

So most know that the biggest function of Web 2.0 companies are their web services, and we really wouldn't be able to access their services, if we didn't have a web browser. There are a few companies who produce web browsers for us, some are for the tech savy crowd, and some are for people who know next to nothing about computers.

Internet Explorer is, of course, created by Microsoft. It has been in version 6 for a few years now, and is currently in a dying state. It doesn't render CSS correctly, and it doesn't even support alpha channel transparent PNG files. This single browser has severely effected the Web 2.0 market.

One of the biggest challenges are cost as most new Web 2.0 companies don't have a lot of money to go around. It is safe to say that companies have pumped tons and tons of time and money into making their services completely compatible with the bugs that Internet Explorer promotes, as over half of all Internet users use IE.

Now the way that Internet Explorer got into such a mess, was years of basically controlling the market, and doing whatever they wanted with it. What they said, went. So when Mozilla came along with Firefox, and basically said "Hey, that's not how CSS is supposed to work", Microsoft was left in the dust, as Firefox moved rapidly ahead in the market, with greater support, for more features (things like transparent pngs and CSS which are a huge part of the Internet now)

Having a 500 pound gorilla doing something incorrectly, and a bunch of small monkeys (companies) doing it correctly, is bound to attract someone's attention. So people started to switch over to the more compatible platform, and as I'm typing this, more and more users are experiencing the magic of Firefox, over Internet Explorer.

Now a split market, is good and bad in some ways. It is good, in the fact that the smaller companies will keep the larger companies in check. So if there are a bunch of smaller companies making better products than Microsoft's' browser, then they are toast!

The bad thing about a split market is the battle for dominance and standards. Right now, to my knowledge, Firefox is still only supporting CSS 2, and other browsers like Safari, are supporting some CSS 3 elements. This makes a pretty big gap. Some companies want to be able to use CSS 3 elements, but have to hold off, because of lack in support.

This really has to change, I think that the top five browser companies, should get together, and have a conference, on what should be done, and how it should be done. Once they all agree, or are at least on common ground, we could move on, with "Browser 2.0".

Browser 2.0 is a simple concept, make it easy for developers and small companies to develop with standards, and quality at the same time. This really has not been a reality, until now, considering a lot of companies say let's just work out the kinks for the majority of people and hope it works for the others, if not, big deal.

I think that the industry is taking one giant step forward with the next generation of web browsers. Microsoft has released it's beta for Internet Explorer 7, and has fixed many of the bothersome, and plain out frustrating bugs that many people have had to suffer through.

Hopefully the final release of IE7 will send out a wake-up call to people, and tell them that they don't have to develop for that broken browser anymore, they can develop for just about any browser, and should be assured that their product will work universally, with all browsers.

Comments - Add New CommentComment Now
It may take up to five minutes for your comment to appear
Submitted by Till on October 6, 2006 - 11:10am.
Subject: But why?

While the concept to create a unified stanard is not exactly new - there is the W3C and many standards to adhere to - I was wondering, is "Browser 2.0" your personal proposal to end the struggle or are you referring to someone else' proposal (Where is the link? ;-))?

I think in general that while for example Microsoft both "enhanced" and neglected the standard for years at the same time, with IE7 they are finally moving into another direction.

If you follow the IE7 blog you see how much they talk about bugfixes (CSS, XHTML, ...) and that is good. At last! And it is because people made them to, not because of some new company policy.

Having said all that, what would "Browser 2.0" do for me? Why not instead support the W3C and all the work already done?

I mean, even if for example Safari would be the only browser to support CSS3 - so be it. As long as it's done according to the standards, let them implement whatever they want, people can use it and build on it and "rely on it" which is common Intranet environments.

I think the problems we see today are not because of what is implemented, but rather how.

Submitted by JakeDahn on October 6, 2006 - 6:10pm.
Subject: Why

I'm highly aware of W3C, and I really do support them. The only problem is that there are browsers, like IE, which do not follow the standards. I think that IE7 is going to be a little more standards focussed, but I still think that there will be a struggle between mainstream standards, and what microsoft says are standards. the whole "Browser 2.0" idea was inspired by what the original aim of this article was focused at. I really wanted to to evaluate the effect of certain browsers, on web 2.0, but the article turned out being more of a "We need better standards!" kind of post. I have nothing against W3C, I support the fully. The only thing that is bothersome, is when a browser or company says, screw that, I'll do my own thing. This is what happened with IE. I think that we need to somehow, enforce the standards, as they come out. So right now Safari supports CSS3, I think that all the other browsers should support the same standards. You said "I think the problems we see today are not because of what is implemented, but rather how." I really agree with this, as you say the problems today. But the problems of tomorrow (after IE7 is out), the problem will be when things are implemented. I think that most browsers will get the idea, as how to implement things, but they will often be outdated. I wouldn't be surprised if IE8 will come after IE7 is really really outdated.

Submitted by till on October 7, 2006 - 8:15am.
Subject: Tomorrow!

But the problems of tomorrow (after IE7 is out), the problem will be when things are implemented.

Not sure I fully agree with you on this, but I can see your point.

For me (as a developer) it's more along the lines of, that I "wish" all browsers would support (for example) CSS2 but also to the full extend of the language and of course according to all standards.

Then I would be able to build websites that work everywhere and do not rely on browser tweaks and switches. So for me the so called "next generation" is not as important as what's going on now. I'd rather see all browsers support CSS2 completely before some take on CSS3.



Zoho

ShoppingAds
Our Partners

cmplt

OrganicStats
read centernetworks anywhere!
Under The Radar
© 1999-2008 CenterNetworks
Home | News | Reviews | Insights | Interviews | Web Jobs | Press Releases | Startup Tips