(defcomp ()
  (~docs/page :title "sx sucks"  (~docs/section :title "The parentheses" :id "parens"    (p (~tw :tokens "text-stone-600")      "S-expressions are parentheses. Lots of parentheses. You thought LISP was dead? No, someone just decided to use it for HTML templates. Your IDE will need a parenthesis counter. Your code reviews will be 40% closing parens. Every merge conflict will be about whether a paren belongs on this line or the next."))  (~docs/section :title "Nobody asked for this" :id "nobody-asked"    (p (~tw :tokens "text-stone-600")      "The JavaScript ecosystem has React, Vue, Svelte, Solid, Qwik, and approximately 47,000 other frameworks. htmx proved you can skip them all. sx looked at this landscape and said: you know what this needs? A Lisp dialect. For HTML. Over HTTP.")    (p (~tw :tokens "text-stone-600")      "Nobody was asking for this. The zero GitHub stars confirm it. It is not even on GitHub."))  (~docs/section :title "The author has never written a line of LISP" :id "no-lisp"    (p (~tw :tokens "text-stone-600")      "The author of sx has never written a single line of actual LISP. Not Common Lisp. Not Scheme. Not Clojure. Not even Emacs Lisp. The entire s-expression evaluator was written by someone whose mental model of LISP comes from reading the first three chapters of SICP and then closing the tab.")    (p (~tw :tokens "text-stone-600")      "This is like building a sushi restaurant when your only experience with Japanese cuisine is eating supermarket California rolls."))  (~docs/section :title "AI wrote most of it" :id "ai"    (p (~tw :tokens "text-stone-600")      "A significant portion of sx — the evaluator, the parser, the primitives, the CSS scanner, this very documentation site — was written with AI assistance. The author typed prompts. Claude typed code. This is not artisanal hand-crafted software. This is the software equivalent of a microwave dinner presented on a nice plate.")    (p (~tw :tokens "text-stone-600")      "He adds features by typing stuff like \"is there rom for macros within sx.js?  what benefits m,ight that bring?\", skim-reading the response, and then entering \"crack on then!\" This is not software engineering. This is improv comedy with a compiler.")    (p (~tw :tokens "text-stone-600")      "Is that bad? Maybe. Is it honest? Yes. Is this paragraph also AI-generated? You will never know."))  (~docs/section :title "No ecosystem" :id "ecosystem"    (p (~tw :tokens "text-stone-600")      "npm has 2 million packages. PyPI has 500,000. sx has zero packages, zero plugins, zero middleware, zero community, zero Stack Overflow answers, and zero conference talks. If you get stuck, your options are: read the source, or ask the one person who wrote it.")    (p (~tw :tokens "text-stone-600")      "That person is busy. Good luck."))  (~docs/section :title "Zero jobs" :id "jobs"    (p (~tw :tokens "text-stone-600")      "Adding sx to your CV will not get you hired. It will get you questioned.")    (p (~tw :tokens "text-stone-600")      "The interview will end shortly after."))  (~docs/section :title "The creator thinks s-expressions are a personality trait" :id "personality"    (p (~tw :tokens "text-stone-600")      "Look at this documentation site. It has a violet colour scheme. It has credits to htmx. It has a future possibilities page about hypothetical sx:// protocol schemes. The creator built an entire microservice — with Docker, Redis, and a custom entrypoint script — just to serve documentation about a rendering engine that runs one website.")    (p (~tw :tokens "text-stone-600")      "This is not engineering. This is a personality disorder expressed in YAML."))))
