IBM getting into the HTML5 authoring game with open source Maqetta
coolthingoftheday.blogspot.com
coolthingoftheday.blogspot.com
What's an acceptable middle ground?
Nowadays, although more browsers fall behind the support curve and the 'newer' browsers approach greater consistency (at least, while comparing the older features), greater variance is beginning to creep into the field in other ways - tablets, netbooks, mobile broadband. It's a constantly evolving arena. An arena which requires agility, skill and grace to succeed in mastering - slow moving toolchains will find it hard to hit the moving targets. Philosophically, wysiwy(m)g tools annoy me, as they're intoxicating to the general market - drunk with new found 'expertise', actual knowledge is maligned, and art is lost. All of a sudden, every guy with a 3d printer thinks he's a sculptor.
Sadly, this has happened before, and will again - and despite my resentment, I have to admit it's just nature - these things will find their own niche. Wysiwyg is not web development. Word is not a DTP tool. They have their place.
A paper document generates code also, like OO.org (LibreOffice) or OOXML. They're pretty good at that, I have yet to meet the first guy manually writing a doc by hand. Html5 will replace those document formats, simply because they're based on paper.
The camp saying current code generation tools suck, are right. The camp saying future code generators will fit your needs, are right also.
Actually, real typesetting is done with LaTeX which is a document markup language. There are WYSIWIG editors (e.g. LyX) but I seen anyone actually using them.
One middle ground for now would be taking a good CMS template and editing that.