Which is why I don't like the proposal: it's not unifying HTML and Erlang, it's compiling string macros into Erlang. Is there any reasons not to embed the interpolation in Erlang directly?
hello(N) ->
Name = <em><? N ?></em>,
<#>
<p>Hello <? Name ?></p>
<p>The <#></#> lets you group
multiple elements, that don't
have a parent, as a single value.</p>
</#>.
(Whether the <X></X> is doing simple string interpolation, or is HTML-smart is left for the reader to decide -- it's certainly overkill for server-side only code.)You could use XSL , i'm pretty sure you never do that.
Any solution that relies on "templating" involves logic in templates. And templating languages are there because they ALLOW separation of concern. A template is independent from the controller that called it. They just share a contract at the data level.
But in the end, if HTML went with <div></> instead of <div></div> then I probably wouldn't mind so much. But I can't agree that no closing tag is more readable because it takes less space, that makes no sense. It might look better.
I would be curious about bandwidth savings but I'm willing to bet in most cases it would make very little difference.