I haven’t written a technology-themed entry for quite awhile now. At least, not in this blog anyway. But then at the moment that my portfolio blog is out of commission1, I decided to write this here.
While I was checking my email, I received one of my daily newsletters from Sitepoint and stumbled upon this particular article: How to Stop Wasting Time Developing for Internet Explorer. The words “Internet Explorer” alone immediately dawned upon me that even after almost a decade of the web designing and development community advocating for all users, businesses, and organizations, there are still a lot of stubborn users, businesses, and organizations who decided to become stubborn lazy asses and stick with the outdated2 abomination that we all know as IE.
I’m one of the few self-proclaimed designers (developers?) who still have to resort to the old and the outdated. I still use a six-year-old laptop which is still up and running (although slower compared to the latest systems today), still using Windows XP3, and using early CS versions of Adobe4 whenever I work with graphics. I still use the handy Notepad++ to do most of my coding with some assistance from Artisteer, SiteGrinder 35, and various WP frameworks like the Ultimatum Theme and Thematic6 as well as pre-made tweaked templates such as Themify.me and Elegant Themes. Even if that was the case, outdated OS or not, IE is still a web designers’ and developers’ atrocity. Goodness, who on earth still uses IE, let alone IE6?
I think there are many of us web designers/developers who are dedicated to using just one browser and yet we have more than one browser installed in our systems. Aside from Firefox, I also have Opera, Chrome, RockMelt, and Safari. I have a habit of switching browsers whenever I’m having a bad day on a particular one. So far among those, I’m still attached to Firefox.
I wish these stubborn “old world” fogies should realize how much we web designers and developers have to keep up with the latest trends. Before, we had to keep our markup structures validated whenever we use XHTML and CSS. Today, we now have the advantage of doing a whole lot more thanks to HTML5 and CSS3. On top of that, since not very many people are sticking to the desktops and the laptops and are now chillin’ at their cellphones, iPads, and tablets, we designers and developers will now have to consort to Responsive Web Design.7 As you know, none of the current mobile devices have IE installed or have IE as the default browser8, let alone having IE6 all the way up to probably IE8 are even compatible to the latest standards of HTML5, CSS3, and of all things, RWD.
Sticking to the decades-old default isn’t just bad and outdated for the technology standards of a business, it’s just simply bad for their business altogether. You can lose potential customers that way if you don’t even avail your internet presence to the general public except for the ones who have the same principle as you. Either that or maybe some businesses were just too cheap to pay their IT department to have all their systems updated, let alone paying an external IT service firm to have them updated. It’s already common sense that technology updates very fast— and I mean very fast. Because of that, we have to do all we can to keep up. Unfortunately, not all of us have the money to keep up with the trends, therefore the logic for that would be to upgrade to the latest when it’s the right time to upgrade.
Sadly, that doesn’t apply to websites and the overall internet presence.
The article I read from SitePoint did give me pointers on what to do should I ever get a client who would request for a web project that would be compatible with the older browsers. The program I’ve been testing, Artisteer 4 RC2, would be a good tool for me to use. The program generates a template (I’m talking about this version by the way) that is compatible with all browsers from IE6+ to getting that same template responsive. Like this new blog theme I just made, for example. It should be compatible with IE6+ (well, I don’t have IE6+ anymore installed so whatever LOL) and I already know that this theme is indeed responsive. It works on my reader tablet and it works on my phone. Too bad the Google Web fonts can’t be read by my phone’s browser because it’s a BB LOL.
Well then. Enough rambling. Back to working on the Q*Bee quilt!
On the sidenote...
- Seriously, I’m going to make a better portfolio layout… [↩]
- and in some cases, dangerous and vulnerable to hackers and spybots out there… [↩]
- Though my laptop is Windows Vista ready, I heard about the icky news about Vista so I didn’t even bother upgrading [↩]
- CS2 to be exact [↩]
- it’s a gift! [↩]
- Thanks SitePoint for the book, although it’s somewhat outdated now because we’re all for Responsive Web Design now… [↩]
- Let’s just call this “RWD” in this case… [↩]
- Unless if you have a Windows phone? I don’t know what Windows phone has, so I can’t really say… [↩]