Shared publicly  - 
 
Internet Explorer

It doesn't matter what I'm working on, if I encounter something that contains the phrase "Use Internet Explorer for the best experience..." or similar, I instantly want to proceed right to the banging my head against the wall step.

All aboard the fail train. Next stop, Flamingturdburg. Population: Internet Explorer.
2
Tyler Gunn's profile photoChris Aldrich's profile photo
6 comments
 
I will at least give apps a BIT of credit if they explicitly acknowledge that they only work with IE. I HATE web apps that have subtle issues when being used with other browsers. I've run into a few online stores where I got an order ready to check out but couldn't actually pay due to stupid IE dependencies.
 
I can certainly see where you are coming from there. My problem, though, is that a web app should never be built to only work properly in IE. I can understand legacy projects, but that's just insane for any new development.

Developer 1: Hey, what's the worst browser platform we can built and optimize this app for?
Developer 2: IE?
Developer 1: Bingo! Let's do it!

Web dev should be approached with cross-compatibility in mind. Most times, IE is the cog in the wheel and hacks or special considerations are needed to accommodate. But, that just begins to skim the surface of why I hate that browser platform...
 
Being that I develop software for a living, my opinion it is usually the result of some of the following:
1) inexperienced programmers no knowing how to make things work in a cross browser manner
2) typically testing is performed on a single browser and theres some inherent assumption that "if it works on the browser I'm using, it works everywhere". Testing on all browsers takes time, and this means money, which projects typically seem to have a lack of.
3) some hard to solve browser incompatibility is found later in the development, left undetected because of (2), and then there is some arbitrary decision to just support browser X, because we know it works.

Yeah, I agree though, cross-compatibility should be considered from the start, but it often ends up being a pain and takes the back seat to other things. Accessibility is my other pet peeve; 90% of websites are completely unusable to people with disabilities simply because nobody ever thinks to design for it.

...and this is why I no longer do web development. :)
 
Web design and dev certainly has its high and low moments, that's for sure. Haha.

IE is last on my browser compatibility checklist, especially the older versions. As you mentioned, countless hours can be squandered chasing stupid IE bugs and unexplainable behavior. Typically I'm happy with cross-browser support for Firefox, Chrome, Safari and maybe a few others. The newer versions of IE have actually come leaps and bounds, so it's not always a total hackjob to get them to play nice, but there are still some aggravating issues. Though, as I fancy myself more of a web designer and marketer than a developer, I often leave a lot of that to my business partner. He's quite adept at dealing with those headaches. :)

Now I'm curious, what type of dev are you into? We're always on the lookout for folks to subcontract out our overflow work to, but it sounds like you're not in the web dev realm any longer...?
 
Thankfully I don't need to open IE on a regular basis. It seems foreign to have to do so nowadays. Lol, I feel bad for my wife as her work forces everyone to use IE 9 or something like that; Gmail doesn't even work properly with it. Haha.

A couple years ago I did primarily web stuff as I worked for a consulting firm. I now work for a company that makes a robotic intravenous medication preparation machine for use in hospital pharmacies. So my work tends to focus on things like planning algorithms, hardware control, and our traditional "desktop application" GUI. :)
 
Ah, very cool. Sounds like some interesting work.
Add a comment...