What do you think of IE?

[MacPC]

I am so very sick and tired of IE.

As a web designer/developer, I am sure you know what a pain in the a$$ IEs are.

Every version of IE is full of bugs and non-standard compliance to the web standard. The Trident rendering engine is just down right flaw. It's so unfortunate that Microsoft have infested the world with its IE c0ckroaches. As a result, we the web designer have to deal with this Microsoft B$es, to clean up Microsoft's garbages.

Google got it right as they stop supporting IE6. But I don't think Google has gone far enough. I am calling on every web designer/developer to boycott all versions of IE.

At the minimum, we should insert a warning to the visitors that they should use Firefox, Safari, and provide the links for them to download.

[Pprakash]

Taking care is better than the removing taking careness.


Because, firfox didnot considered even if you do some mistakes in htm code, javasciprt etc, this firfox browser avoid that mistakes make them as correct in its own.


But, I.E. show any small mistakes if you do. Then it is helpful to us which is correct, which is wrong.


Think agian

[tirna]

As a website developer I don't mind IE.

Yes it has it's perculiarities, but so do the other major browsers. The way I get around them is to have a separate external css file for each of the browsers I support - IE, FF, Opera, Safari and Chrome.

Most of the time I would say there is less than 10% difference in their content. The differences only occur when one browser does something diffrently to other browsers and so I set up that browsers css to suit without affecting how a web page renders in other browsers.

It only takes a minute to copy any style changes for a web page to the stylesheets and maintenance for me is very easy.

Normally, I set up a web page to render correctly in IE8 and then make a copy of the IE8 stylesheet for the other browsers. I then open the web page in the other browsers and tweak their respective stylesheets if necessary. All this takes me no more than a few minutes.

This way I don't waste time making changes in a single stylesheet for the whole website for one browser and find it breaks a web page in another browser.

I have a JS function which detects the browser making the request for the web page and then links the appropriate css file for that browser in a <link> element.

[Sunny G]

MSIE is one of Microsoft's meek attempts to make a decent piece of software with any set of standards in mind. It does its job, but little more. We can deal with it and not invest emotion into the subject for our own sake.

[NogDog]

Whether or not I like it is beside the point if I want to be a professional web developer. Since the vast majority of web users still use IE, I must support it, or else I am doing my clients a major disservice. The only exception might be in a corporate environment where the users' client software is controlled and they have chosen to make some other browser the standard. (And the fact it, in most such situations, IE will be the standard.)

Frankly, I find that if I generate well-formed [X]HTML (including doctype declaration!) with reasonably applied CSS, I seldom have any trouble supporting IE7+ along with all the other major browsers -- maybe very occasionally having to use an IE conditional comment or two to handle a quirk here or there.

[tirna]

..........Frankly, I find that if I generate well-formed [X]HTML (including doctype declaration!) with reasonably applied CSS, I seldom have any trouble supporting IE7+ along with all the other major browsers.........

Totally agree :) although I am against using IE conditional comments because they are IE specific....but that's just me.

[Jarrod1937]

The problems with IE come if you attempt to do any type of advanced styling that requires some obscure (but standards compliant) css rules. That is where i have my trouble at times. Sadly though i must still support IE6 for my main client, yet also advance the site with the latest e-commerce features... now that is fun :-/
I personally feel IE's DOM renderer needs to be retired. Every site feels slightly sluggish but only because of the way its renderer handles the pages. Firefox renders pages faster, and google's chrome does some black magic behind the scenes and renders the pages even faster.

"At the minimum, we should insert a warning to the visitors that they should use Firefox, Safari, and provide the links for them to download. "

Haha, trying running an e-commerce site, doing that, and seeing how your client reacts as their profits are cut in half. Me thinks that approach wouldn't go over so well ;-)

[slaughters]

Safari and Firefox are full of bugs and quirks as well.

The two I run against most often are that stupid Firefox memory leak and that equally stupid Safari outline bug for anchor tags and IMG's

[JPnyc]

Actually most of the time I found you can get by without using any IE specific code. So far the only exception would be transparency, and fixed background in elements other than the body

[Xerond]

It has been a long time since I've been forced to use IE to view a site. I was a firefox convert a good five years ago and that lasted for a while. Chrome has been my browser of choice for the last year though, and while it does still have compatibility issues here and there, the overall time that it has saved me with speed and efficiency has more than made up for it.

[JohnTriger]

IE8 has gotten better - almost want to ditch firefox now...