Skip navigation
BLOG  |  MARCH, 2009

The Future Will Be a Mix of Old and New

March 17, 2009 at 8:00 am
by

In a post for Core77 entitled "Beyond the Scholock of the New: Eight Strategies for Design and Foresight" Kevin McCullagh writes:

"The future is always a mix of revolutionary change and evolutionary continuity--and sometimes regressions are in there too. Unlike the Star Trek view of the consistent future, many of today's trend-setters enjoy gaming on iPhones and organic gardening."
Kevin McCullagh, Plan

This is true of the technology we use every day to serve our clients. We have clients that are still running versions of our NewfangledCMS from over 4 years ago, yet have made upgrades to their site to reflect current trends (i.e. updated interfaces, advertising tools, blogs, etc.) on an ad hoc basis.

There are two conclusions I can think of in response to this phenomenon. The first one is negative: adding current functionality to an outdated system will only get you so far. In most cases, the reason we don't upgrade these sites fully to the latest version of our CMS is due to a lack of funding. The quick upgrade is prioritized over the long term stability of the entire system. This is not a great philosophy to have, especially not for your website, which is the most important and powerful communication tool your business has. Sure, you'll have a blog, but when that next most popular browser comes out and leaves IE 6.0 (the browser that was the new hotness when your site was first built) in the dust, it might look at your site and spit it out backward for all we know. That's the trouble with browsers- developers can't always anticipate how Microsoft, Mozilla, Apple, or Google will engineer their software, so what works on today's browsers may not on versions that have yet to be released. The blog won't help much when a user can't even see the website properly.

But, the second conclusion is the positive spin on this. The disaster scenario I described just now doesn't happen much. This is because our CMS was created by people who think long term and made it a goal to build a system that would last. Mike Boulet, our CTO, is the kind of guy who uses his laptop to plan out his do-it-yourself passive solar mods to his house, or his springtime planting of many tomato plants next to his backyard chicken coop. He's got his feet firmly planted in the realistic future that McCullagh describes above. So, even though we've worked our way to version 5.0 of our CMS, sites still running much older versions are being kept alive and well with the occasional check in and tune up. While it works, I think that's pretty great.


Comments
Nolan | March 17, 2009 10:00 AM

On your first note about future browsers that possibly "might look at your site and spit it out backward," these situations are becoming less and less likely. I'm a big standards nut for this EXACT reason.

Browsers now make it a high priority to stick to W3C standards. Newer browsers try to give the end user a high-level of confidence that if a site is built to proper standards, it will be rendered as expected.

Most of the mess-ups that become present as newer versions of browsers are release are caused by the older site not adhering to the standards as well as it should. The browsers try to remain backwards-compatible as much as possible, but given the option between standards compliancy and backwards compatibility, they usually choose to comply.

Picking a common doctype (http://www.w3.org/QA/2002/04/valid-dtd-list.html) and then validating your site against it will ensure that you are "future-proofing" your website, so to speak.
Chris | March 17, 2009 10:23 AM

Nolan,

Great point! It's true, sometimes I still have my head in the 'old days' of browser issues, but you're right that this is the whole point of standards. Our desire to build according to those standards is definitely a future-oriented approach that just makes sense. Of course, any CMS user can still populate their site with custom HTML that is likely to not be standard, so the 'oops, it's broken' in whatever new browser comes along is still a possibility.

Chris
Tom | March 19, 2009 11:21 PM

IE8 was just released, and it's already getting some buzz for having "leapfrogged" Firefox. But then FF will probably release an update to v3, and then Chrome will probably follow up too. When will the browser wars end?