Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

S-expression HTML as Standard

Name: Anonymous 2013-09-17 13:25

Who the fuck thought it would be a good idea to use opening and closing tags as DA STANDARD for SHITML? Are the people at W3 dumb?

For those who don't know what I'm talking about,
look how ugly and unnecessarily long HTML is.

<html>
<head>MY WEBSITE</head>
<title>MY WEBSITE</title>
<body>
<p>THIS KIND OF MARKUP IS <b><i><u>SHIT QUALITY</u></i></b></p>
</body>
</html>


But compared to the S-expressions

(html (head "MY WEBSITE")
(title "MY WEBSITE")
(body (p "THIS MARKUP IS" (b.i.u "SATORI QUALITY"))))


It looks far cleaner and makes your eyes feel right at home. It's easier to parse and won't take up as a few kilobytes / megabytes (depending on the page) less Internet bandwidth. Sure it has a lot of parenthesis but it's more attractive than the repeating shitstorm of </tags>.

I know there are a lot of implementations to this but there should be one STANDARD to rule them all. The next version of HTML in the standard should be something like this.

Name: Anonymous 2015-11-03 4:32

>>65
Formatting SGML in a shitty text editor:
Most people just write it all left-justified anyway, so there's nothing to format.
Including the tag name in the closing tag makes it easy to figure out where you are in the tree, even if you lack indentation to convey the structure.

Formatting C and most Algol-like languages in a shitty text editor:
New scopes and scope-like constructions require an indentation level. Hit tab 1-4 times before you type. If you need more than 4 indentation levels or so, you're probably doing something wrong.

Formatting sexps in a shitty text editor:
Small sexps are inline:
(* 2 4)
More complicated sexps that are split across multiple lines have each parameter indented to the same amount.
(+ (* 3
(+ (* 2 4)
(+ 3 5)))
(+ (- 10 7)
6))

Spaces are required to properly indent this code. It's a lot easier to indent 1 tab per indentation level than it is to spam the space bar twenty times in the kind of deeply-nested code that Lisp encourages.
If you change a function name, every sub-expression is now improperly aligned, and you will have to realign them manually:
(plus (* 3
(+ (* 2 4)
(+ 3 5)))
(+ (- 10 7)
6))

And if you don't follow these rules, it quickly becomes extremely difficult to follow your code.
More importantly, shitty editors lack paren matching, so you'll be wasting tons of time manually counting parens and running into subtle bugs when you make mistakes.

This never ever would have flown with the tech-illiterates copying and pasting their way to their first homepage that drove the early web.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List