Skip to main content

IE6 Downfall Is Coming, The Nail in the Coffin for IE6

The tides of darkness are slowly subsiding. I've come from a generation of front-end developers that have had to deal with every single IE6-related layout or JS bug in the book. Incidentally, I've been looking at the latest browser statistics on W3C and although your particular client may have more IE6 users, we can't deny the fact that the IE6 unicorn is about to die off in the coming years. It is happening. The day that I thought would ever come is edging closer and closer as I look at these web browser usage statistics.

My current client has mandated that all their sites drop IE6 support. This is a client that pulls in a huge amount of traffic hits a day and anyone who visits the site on IE6 will be thrown this message: http://code.google.com/p/ie6-upgrade-warning/.

This brings me to my question: are IE6 heroes needed anymore with declining usage? Do you remember the days when a client wouldn't launch the site because of IE6 performance issues? Do you remember when your client was raging about transparencies/drop shadows not being pixel perfect? Those were the good old days of broken bones, blood, and sweat. Newer developers that are coming into the front-end development scene don't deal with these kinds of issues at present day now that clients realize how terrible IE6 is and how 5% of traffic isn't worth doubling the budget on bug fixes. Have times changed, has launching a site become easy mode?

Good luck and have fun,
Jaime Bueza

Jaime Bueza is a software developer in Vancouver, British Columbia, Canada. He has developed web applications for Nintendo, Electronic Arts, Ritchie Brothers, Kiwi Collections, and Cox Communications. When he's not developing useful software that constantly evolves with business requirements, he's creating tutorial videos for aspiring front-end developers.
Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.

Cheers,
Jaime

World of Warcraft Ninjalist addon: version 0.1 coming along quite nicely

After toying around with more GUI related issues in World of Warcraft's API, I've decided to take a totally different direction. Originally when I architected this addon, I knew in my mind it would be a super simple Console application that a user could easily paste in a name and add it to the database; however, why stop there?

After discovering AceGUI, I can easily start developing UI components in no time! As of right now, I've got it saving data in between game sessions--the interesting part will come when I'll have to develop the web service that will parse the SavedVariable.lua, eliminate duplicate entries, as well as, do a huge merge between their copy and whats on the server's (per realm basis of course).

Here's a screen shot of the responses when adding new Ninjas to your list:
When a user clicks add after entering a name in the textbox, it'll go ahead and add that person to the ninjalist tagging the user's realm and current date/time. Someday, I…

Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:



Now, whenever you make a commit, it should show up like this in the log:



Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this



Want more emojis? check out the Emoji Mardown Cheatsheet!