xybermatthew

Today I had a conversion with my friend Brian and he asked me what I liked most about my iPhone. Even though I’ve only had it for a week now I had commented to him that I like how it’s made my life more productive. I’ve been able, with the help of plaxo, to sync my calendar and tasks as well as my contacts and with email integration stay in better contact with family, friends, and my clients. I also mentioned that as a web guy having the Internet always in reach is a nice feature — and I don’t know how I lived without it! Also, as a side note, IMHO it’s the best UI for a phone/PDA/iPod.

PS I wrote this post using my iPhone!

I’ll be brief.

I read Aaron Gustafson’s article on moving away and beyond the DOCTYPE as the only solution for setting up the correct parsing engine within browsers and for the most part I agree with this suggestion of using “version targeting” as a means of taking control of how sites should be displayed and protected from browser upgrade issues.

I also say that this isn’t the “silver bullet” of answers to the dilemma — and I think it’s obvious when you read it; however it would be a huge step in the right direction.

My other concern would be the bloat of the browser size — it would have to accommodate older browser rending engines and possible other browser rending engines too. Perhaps if an end-user comes upon a site “tagged” for an older or other browser environment the end-user could be prompted to install a “plug-in module” for such rendering engine.

…define a list of browser versions that the site was built and tested on, and then require that browser makers implement a way to use legacy rendering and scripting engines to display the site as it was intended—well into the future.

Here’s to the future of web design and development. Thank Aaron for the suggestion.