51–60 of 72 posts
If you're still looking for a name let me suggest "hyper text". It embodies the whole idea of having data, code and presentation at the same place. If you're open for contributions I already have an idea for cascading styles system in mind.
[given what CSS has incrementally and inevitably become, it's my ever-firmer belief that DSSSL would've been the right choice in the first place]
Very cool. I'm imagining using this with Claude Code, allowing it to wire this up to MCP or to CLI commands somehow and using that whole system as an interactive dashboard for administering a kubernetes cluster or something like that - and the hypothetical first feature request is to be able to "freeze" one of these UI snippets and save it as some sort of a "view" that I can access later. Use case: it happens to buil…
Exactly this! Right now this uses React for Web but could also see it in the terminal via Ink. And I love the "freeze" idea — maybe then you could even share the mini app.
Brainstorming, perhaps ` >`? It goes against the grain of "eval() line-by-line", even if it's handled ASAP. But it might relax the order constraint on codegen. Especially if the UI gets complex, or rendered on a "pane off to the side".
Earlier quoted context omitted.
Exactly this! Right now this uses React for Web but could also see it in the terminal via Ink. And I love the "freeze" idea — maybe then you could even share the mini app.
Did you see that Claude Code just came out with "channels" that allows for messages to be injected into the session/sent out by claude via hooks and MCP server [1]? I had CC code an integration between fenced and CC using channels and it actually worked - a little clunky since there is no streaming, but very interesting nevertheless. [1] https://code.claude.com/docs/en/channels-reference
https://a2ui.org/
My approach is the opposite bet: full code execution instead of tool calls. The agent can build any React UI from scratch with the full power of code — including client-server data flow, callbacks, streaming data.
Brainstorming, perhaps ` >`? It goes against the grain of "eval() line-by-line", even if it's handled ASAP. But it might relax the order constraint on codegen. Especially if the UI gets complex, or rendered on a "pane off to the side".
Earlier quoted context omitted.
If HTML happened again except this time it was markdown, maybe more non-nerds would be able to use it? XML just looks gnarly.
Problem with the markdown approach the text will become rapidly ugly with hacks, non-standard annotations to enable same features as HTML.
What are some of the ugly hacks you've seen that were applied?
If you're still looking for a name let me suggest "hyper text". It embodies the whole idea of having data, code and presentation at the same place. If you're open for contributions I already have an idea for cascading styles system in mind.
Perhaps "WWW SPA document"? Using markdown with highly-progressive fenced blocks?
Hypertext (one word, coined 1960s) is quite a broad category. Subcategory "WWW" could fit, as TFA seems WWW-ish. A markdown document format, and progressive rendering of tags and code, seems HTML-like. Though with greater progressiveness - code blocks with streamed execution rather than merely compilation. The progressive JSON callbacks, React, integrated client and server code execution, and server-side rendering, seem closer to WWW SPA than to HTML. Though SPA files often seem more "source" than "document". And the multiple-page "App"-ness of SPA doesn't fit well. SPA seems a better fit than "full-stack". Perhaps some name analogous to "isomorphic javascript"...?