But technically, DSSSL (OpenJade) was used to render pages to print/PDF and never ran as part of a browser stack (unless I've overlooked some stubborn Schemer implementing it in JS or emscripten or sth; but don't tell HN's Lisp fraction to given them ideas ...) Unlike SGML itself, which is mentioned in TBL's docs as the basis for HTML markup. Btw SGML does have its own styling language in link processes which basically just re-uses regular attribute declaration syntax, plus has some explicit state machine representation (aka "links").
But yeah, using a Lisp derivative would've definitely prevented the syntax proliferation that is CSS, its terseness/magic, and habit of re-use of property names for different purposes as a way to sneak in complex layouting features by understated surface syntax changes.
But technically, DSSSL (OpenJade) was used to render pages to print/PDF and never ran as part of a browser stack (unless I've overlooked some stubborn Schemer implementing it in JS or emscripten or sth; but don't tell HN's Lisp fraction to given them ideas ...) Unlike SGML itself, which is mentioned in TBL's docs as the basis for HTML markup. Btw SGML does have its own styling language in link processes which basically just re-uses regular attribute declaration syntax, plus has some explicit state machine representation (aka "links").
But yeah, using a Lisp derivative would've definitely prevented the syntax proliferation that is CSS, its terseness/magic, and habit of re-use of property names for different purposes as a way to sneak in complex layouting features by understated surface syntax changes.