Skip to main content

Web Browsers You Should Support

As a web developer, generally speaking, you should consider supporting the following browsers (at the time of this writing):

  • Chrome (latest) - the browser that sets the bar for the others; you should be using it and supporting it
  • Internet Explorer 9+ - the browser that finally caught up with the times a bit; basically, a Chrome wannabe.  I still say that IE sucks... even if it really doesn't anymore.  Yes... I'm sour about IE8 and below.
  • Internet Explorer 8 - the old, sad browser that we sadly still have to support for a while.  CSS 3 is not well-supported here, so we use projects like CSS3 PIE or whatever.  By the way... IE8 sucks.  I can't wait until this comes off of the list.
  • Firefox (latest) - the browser that was once awesome and has sadly suffered recently because it's slower than Chrome... but hey, lots of people still use it.
  • Safari (latest) - Watch out for Safari as more iPhones, iPads, Macs, and more overly-priced Apple products flood the market and artificially drive Apple's stock price through the roof
  • Mobile - If you support Chrome, your site will probably work on Android, and if you support Safari, it will probably run on the iPhone and iPad.  The only work left to be considered is supporting various screen sizes with responsive web design.
Hmm... who didn't make the list?  Here are the browsers you should not consider supporting:
  • Internet Explorer 6 - fewer than 1 out of 200 people still use IE6 world-wide.  Unless you are building a website for the Chinese (who are a bit behind the times with IE6 usage over 10% and falling), you should NOT consider supporting IE6.  Instead, save hours of your life.  If a colleague or friend decides to support IE6 for their web app, you should laugh at them.
  • Internet Explorer 7 - with less than 2% usage world-wide, don't waste your time on IE7's poor support and stupid bugs.  Instead, save even more hours of your life.  Trust me on this one; you are better off thinking about responsive web design than supporting a dying legacy browser.
  • Any other browser (like Opera) - these browsers aren't being widely used, and to be honest, these browsers often support web standards the best... kind of like Chrome.  So, if you support Chrome, your site will very likely work in Opera or any other off-the-wall browser out there.
If an unsupported browser hits your site, be nice to the user.  Here are some suggestions:
  • Explain to the user why they have an unsupported web browser, but most importantly, tell them how to upgrade.
  • Send IE6 and IE7 users to the IE8 download page
  • Send IE8 users running Windows Vista or Windows 7 to the IE9 download page
  • Or maybe... send all IE users to the Chrome download page  :)
  • If any other unsupported browser hits your site, just let them be.  Don't warn them or anything unless absolutely necessary.  They probably know that they are using a old or off-the-wall browser, and if not, then they are among a small percentage of the population that won't be able to use your website.  Oh well...

Comments

Post a Comment

Popular posts from this blog

Developing a lightweight WebSocket library

Late in 2016, I began development on a lightweight, isomorphic WebSocket library for Node.js called ws-wrapper .  Today, this library is stable and has been successfully used in many production apps. Why?  What about socket.io ?  In my opinion, socket.io and its dependencies are way too heavy .  Now that the year is 2018, this couldn't be more true.  Modern browsers have native WebSocket support meaning that all of the transports built into the socket.io project are just dead weight.  On the other hand, ws-wrapper and its dependencies weigh about 3 KB when minified and gzipped.  Similarly, ws-wrapper consists of about 500 lines of code; whereas, socket.io consists of thousands of lines of code.  As Dijkstra once famously said: "Simplicity is prerequisite for reliability." ws-wrapper also provides a few more features out of the box.  The API exposes a two-way, Promise-based request/response interface.  That is, clients can request dat...
Post a Comment
Read more

Wedding Prediction - October, 2013

Carla and I are planning on getting married sometime in October next year.  We need to pick a date, and that decision may  involve some science and mathematics.  :) For example, we want the weather to be nice.  To be more precise, we'd like the high temperature for the wedding day to be between 60 and 80 degrees Fahrenheit.  Obviously, we have both lived in Ohio our entire lives, and we have a pretty good idea of what the weather will be like.  We both hypothesised that October was a "hit or miss" sort of month; it could be cold, or it could be nice. But, for me, a simple hypothesis was not enough; I really wanted to know the probabilities of decent weather based on historical weather data.  Many websites on the Internet (i.e. almanac.com) charge you to review historical weather data, but Carla and I discovered a cool page on cleveland.com that provided exactly what we wanted.  I loaded the historical temperature data from 1903 to 2011 f...
2 comments
Read more

Data Persistence in Various Databases

This blog post will cover the varying levels of data caching and data persistence provided by various operating systems and database systems. Cache  - A device placed in front of another storage device that is used for temporary storage of data.  The use of a hardware cache is often transparent to the end user and is generally smaller, faster, and less persistent than the backed storage device.  Rather than reading/writing from/to a slower storage device (i.e. a hard disk), we read/write from/to the cache (i.e. RAM, NVRAM, etc.). Reading from a cache is simple.  If the datum we requested is in the cache, we simply read it from the cache.  If not, we need to retrieve the datum from the storage device and place it into the cache (often a much slower operation). There are different policies when we write to the cache, though... Write-Through Cache Policy  - When using this policy, writing over the cache also writes over the data on the backed storage d...
Post a Comment
Read more