Interesting read. To be honest I didn't think anyone was working on HTML any longer, I figured any more advances will be in things like CSS, XML and JavaScript, it's good to see that that's not the case. I do agree however with some of the comments below the article - a more pressing issue right now is browser compliance. I'm tired of having to design websites for two or three browsers. IE7 was suppose to resolve that issue to a large extent, but other than native PNG support I still find myself having to use all the same old tricks to make sure that pages look similar on IE7 and FF, and note how I say similar, because other than in very limited cases it's almost impossible to make them look identical, unless the whole page is flash.

FF2 isn't exactly perfect either. It was suppose to be 100% CSS2 compliant - but it's not, and while generally better off than IE7 there are still some oddities that crop up here and there - like the "background-color" area behind linked images.

Why is it so hard for them to make 100% compatible browsers

I disagree. I find it fairly easy to make it all identical across browsers. Of course, I use a cross use of CSS and HTML. Although CSS is said to completely eliminate HTML, I find that a combination is best.

If your very specific about what you want, everything tends to mesh well. The latest problem I had was actually with Firefox, where it wouldn't accept one of the marquee options for my matrix look (and I didn't want to use Javascript for those who didn't allow it). Getting my multiple sound media player to work also posed a few challenges.

Some new standards would be nice... But it's like in 4 years?!? The final days of 2010? Ugh, that's quite a ways away... but I guess it'll come quickly.

Oups...honest typo...



Well nothing much, it's just CSS 1.0.



True...this works very good. CSS for layout elements and HTML for everything else. But that's for small/personal sites. Not big sites IMO.

This site uses CSS.

A big website with many pages will benefit from layer separation so that it's easier to manage it. If you have 50 pages, or more even, you don't want to iterate through each page to update your layout. That's why you put everything into one external CSS file.
And if you have a big site you most likely want to make your content accessible to as big an audience as possible. So you want to cater for normal web browsers, people with accessibility problems, mobile phone access perhaps (the web isn't just for computers any more. even TVs access the internet) and you might want to provide a customized print layout to match your company profile and remove any element not related to the content such as the navigational links etc.
If you where to do this with the layout defined inside you HTML then you'd have to create a page for each of these scenarios. Something which will cause more time to be spent and as well as bandwidth.
If you separate the layout from the content completely all you need is one HTML file for each page and a set of CSS files which the browser will choose from according to it's needs. Screen readers will load your aural CSS file, moble devices will load CSS designed specificity for small screens and when you print you get the special print layout.
You have then removed the need for multiple pages for the same content, whilst modularise your design into smaller manage pieces. Additionally the CSS files will be cached normally by the user agents so you will save even more bandwidth.

Separating layout from content, as well as behaviour (javascript) isn't any harder that old tag soup. It's just different. But it's benefit hugely outweighs not using it. Particularly as the site grows.