HTML, CSS and JS as TOON #220
Replies: 1 comment 4 replies
-
|
Hi there, interesting idea, but this is out of scope for TOON. TOON is intentionally limited to being a lossless, deterministic encoding of the JSON data model ("JSON in, JSON out"). Extending it to HTML/CSS/JS would mean inventing a separate templating/markup language with its own semantics, and there are already many established tools for that space – Pug/HAML/JSX/etc. To keep the format focused and predictable, I'm not planning to pursue this direction. |
Beta Was this translation helpful? Give feedback.
-
|
That sounds reasonable, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
@johannschopplich could you elaborate on the other tools? in terms of token efficiency/speed up/increase accuracy when working with HTML file? |
Beta Was this translation helpful? Give feedback.
-
|
My reasoning was not that TOON would emcompass HTML, CSS and JS but rather separate formats. It was just TOON that got me thinking. Maybe also because I think that driving them forward as a collection would visualize how much we would save in data transfer and storage. The Hello World! example above would be a 75,7% reduction in token "cost". But like I said, TOON is TOON. An optimized HTML version would be something like LLML (Large Language Model Markup Language). |
Beta Was this translation helpful? Give feedback.
-
|
@rasmuswikman a reduced version of HTML in the style of TOON really sounds like the pug templating language: //- layout.pug
html
head
title My Site - #{title}
block scripts
script(src='/jquery.js')
body
block content
block foot
#footer
p some footer contentYou could instruct an LLM to render markup in pug to save in token output cost, and then transform it into HTML locally. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What if you extended the idea of TOON to HTML, CSS and JS?
Eg.:
Would become:
Beta Was this translation helpful? Give feedback.
All reactions