With the life of IE6 coming rather slowly to an end (as discussed in my previous post), the talk of designers and developers dropping support for the browser is rife in blog posts and tweets all over the web.

Some pretty large sites have already got the ball rolling - possibly one of the biggest being FaceBook.

There is also a trend of developers, not dropping support entirely, but only providing it if their client specifically requests and pays for the work necessary to accommodate the browser.

So, where do I stand on IE6 support?

Well, I'm not telling you. Nah, only joking. Read on my little chickens ...

Yep. You have read that correctly. I will miss IE6.

Yes, it is an awful browser - full and stupid bugs, limitations, poor standards support, yadda yadda. We all know this. We've all beaten our fists on our keyboards in frustration when trying to get things 'working' in it. We've hacked it, and metaphorically smacked it, since the day it first launched back in 1507 (or around that time).

I have hated it. I have wanted it to die. It has often cost me money in extra development time on projects, and held me back on certain interesting ideas I've wanted to implement on commercial work.

"Yes. That's right. So why in the name of Jiminy Christmas will you miss it?!"

Well, give it some 'click' and I'll tell yer ...

Every body's doing it, doing it, doing it, picking their nose and chewing it, chewing it, chewing it ...

Nah. "Tweeting". That's what everybody is doing.

Twitter.com has been big for quite a long time, especially within the geek community, and now it's gone well and truly "main-stream". You can't move for tweets from Dave Grohl telling you he's 'just had some toast', or Gorden brown announcing that 'the downstairs loo is blocked' (made them up btw :P).

I will be warbling on about what it is that makes it fly, and what about it makes me spit feathers (you can't beat a good pun or two :P) ...

An article discussing my experience with the rather spiffing Content Management System: Expression Engine, as used on my t'other website: www.kevadamson.co.uk.

"... It's not perfect, but no CMS is. It also requires a lot of learning and reading, which may annoy those who want something more plug and play. But I imagine that - if you learn the system inside out - the rewards are: plenty, and any compromise: few ..."

As I mentioned in my recent post: "OMG! It's alive!", this here very website has its own bespoke CMS (Content Management System) for updating portfolio examples, blog posts and all the content on every page.

I'm no PHP programmer, while my friend and colleague Graham (of behinddesign.co.uk) is. And tis he who is to thank for all the PHP wizardry that's going down on my new site. Thanks Graham. Thraham.

Let me tell you more about this rather talented chap.

Our story begins many, many years ago, in a cozy little office above a chemist ...