Question

I’ve been writing a source-to-display converter for a small project. Basically, it takes an input and transforms the input into an output that is displayable by the browser (think Wikipedia-like).

The idea is there, but it isn’t like the MediaWiki style, nor is like the MarkDown style. It has a few innovations by itself. For example, when the user types in a chain of spaces, I would presume he wants the spaces preserved. Since html ignores spaces by default, I was thinking of converting these chain of spaces into respective  s (for example 3 spaces in a row converted to 1  )

So what happens is that I can foresee a possibility of a ton of   tags per post (and a single page may have multiple posts).

I’ve been hearing alot of anti-&nbsps in the web, but most of it boils down to readability headaches (in this case, the input is supplied by the user. if he decides to make his post unreadable he can do so with any of the other formatting actions supplied) or maintenance headaches (which in this case is not, since it’s a converted output).

I’m wondering what are the disadvantages of having tons of   tags on a webpage?

Answer 1

If it’s just being dumped to a client, it’s just a matter of size, and if it’s gzipped, it barely matters in terms of network traffic.

It’ll slow down rendering, I’m sure, and take up DOM space, but whether or not that matters depends on stuff I don’t know about your use case(s). You might be able to achieve the same result in other ways, too; not sure.