Bas said:
*snip*
I think a lot of the problem is how ill-conceived the basic/fundamental existing stuff is. That's certainly what seems to waste much of my time whenever I design a webpage. We don't so much need new stuff as better stuff. Most web standards should be taken
outside and set fire to, then replaced with something better, except it's too late now and we're stuck with the stupid things.
I mean, who the heck creates a layout system that doesn't allow for one item's x and y positions, widths, heights, etc. to be relative to other items'? (Sure, CSS can do it in a few cases, but they are exceptions and not the rule. You cannot say that one
div should have the same height and half the width, and be placed relative to, another arbitrary div. You definitely cannot take properties from multiple other divs. What an absolute crock of failure.)
Then again, I could say the same about most desktop UI frameworks. 
Basic XML itself is okay and useful but the technologies (and specs, documentation/books/etc.) layered on top of XML are pretty awful, on the whole. (Pet hate: Specs/docs which talk about things they haven't actually defined yet, without even telling you
they haven't defined them yet, for great confusion, re-reading and wondering if you accidentally skipped a page somewhere.) I mean, if XSLT didn't suck so much it could've done what CSS does so much better, IMO. As it is, I'd sooner convert XML content into
HTML via C# or C++ code than mess with XSLT, and that can't be right.