I was disappointed to read that iWeb, Apple's new WYSIWYG editor, generates pretty crappy code. When I read Roger's post and saw the examples, my initial reaction was, "At least it's using divs! It isn't peppered with the font tag and deprecated attributes, like the code Frontpage generates!" But then I remembered that "not sucking as badly as Frontpage" shouldn't be the gold standard for WYSIWYG-generated code. And while using CSS instead of tables for layout is nice, all the inline styles and nested divs really obfuscate the point of this methodology. It reminds me of a former co-worker, struggling to learn CSS against his will, who said, "When I built this page I tried to use as many divs as possible."

iWeb-generated pages do validate, which makes me roll my eyes a little less dramatically than if it produced the 9,547 errors typically found in Frontpage-generated HTML. But again, let's remember this mantra: Valid markup does not necessarily equal good markup.

C'mon, Apple, don't let us down now... you can do better!