For all I know, my macroexpansions are ugly too. The whole point is that I don't have to look at them.
For all I know, my macroexpansions are ugly too. The whole point is that I don't have to look at them.
The usual alternative to html-as-object-code is to use a template system, but template systems seem to move as a group (and individually during development) toward being a way to write your usual language, but surrounded by HTML, which has the same problems I outline above, since the designer still has to mess with what's really application code. I suppose this is because template systems are usually designed by programmers, for programmers.
In fact, there are many, many exceptions to my general rule that you'd want to eventually turn over HTML/CSS/design stuff to a designer, and news.yc is one, probably. But the vast majority of my projects are no exception, and I'm fortunate to be married to a designer with strong opinions on the matter, so I get good feedback. :)
One of the promises of the web was that interface could be cleanly separated from the application itself, and it seems to me that most approaches being used today throw away that promise because the programmers assume that UI and design aren't important, or aren't hard.
Another thing, is that you could reduce the HTML code a bit by using CSS more. The following example shows a <font>-tag inside a span...
<span class="comment"><font color=#000000>
But I do note the board does work well: is always up, does what it's supposed to, is easy to use, seems secure, and thus it just doesn't matter.