4 ms·
It seems to me that Lisp-generated websites tend not to have valid HTML. I've often wondered if there is something about Lisp that makes people averse to valid
by nertzy 18y ago
It seems to me that Lisp-generated websites tend not to have valid HTML. I've often wondered if there is something about Lisp that makes people averse to valid HTML.
Are there easy ways in Lisp to make sure that you are outputting valid HTML? Like good libraries for escaping text and making sure the proper tags are closed the right ways?
Anyway it's not such a big deal since the sites work fine in browsers. It's more of a passing observation, that really probably extends to other programming languages as well. I just think that something about the structure of Lisp makes HTML/XML feel sloppy and thus there is an unspoken bias towards not worrying about it.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.roxority.com%2Froxbase%2F&charset=%28detect+automatically%29&doctype=Inline&group=0 http://validator.w3.org/check?uri=http%3A%2F%2Fwww.roxority....
http://validator.w3.org/check?uri=http%3A%2F%2Fnews.ycombinator.com%2Fitem%3Fid%3D197019&charset=%28detect+automatically%29&doctype=Inline&group=0 http://validator.w3.org/check?uri=http%3A%2F%2Fnews.ycombina...
- dualogy 18y agoNope, at least in my case the HTML is not Lisp-generated, but hand-written. I use the templating way where occasionally I insert server-side Lisp code in what is otherwise mostly mark-up. Of course it is not "something about Lisp". The HTML is always generated by a human, either "manually" (as in my template library) or automatically (as in CL-WHO or home-grown s-expression-to-HTML macros). But you're right, it's not a big deal. What matters is the browser and the user, not the W3C :)