Comment by rbalicki
7 hours ago
"For AI agents". I understand why everything needs to be marketed in this way, but it's just ... an easy-to-generate language for expressing charts. That's impressive! That's useful.
7 hours ago
"For AI agents". I understand why everything needs to be marketed in this way, but it's just ... an easy-to-generate language for expressing charts. That's impressive! That's useful.
Isn't this literally made for AI agents to be accessed through an MCP server? Seems to me the AI agents part of the marketing is important.
But why be exclusive? Why not "Chart language for computer programs to generate"?
I don't want to use an agent at all, but i wouldn't mind generating some charts with an easy-to-generate markup language...
But for that we already have mermaid.js (and its precursor Graphviz/dot).
The only reason to use this instead of existing, mature ones designed for humans is if you are an AI agent.
4 replies →
Careful, they'll spring something XML-derived on us.
Because these are completely different requirements.
1 reply →
Did you read the post? It directly answers why this is specifically for AI agents.
for agent to generate, but also easy for human to edit (especially with UI) :)
also worth noting that Vega-Lite is literally just fucking that and AI already does good job with producing JSONs for it
I work with someone who did a lot of work with this to improve our ability to generate awesome visualizations with little thinking. It's a very powerful language but needs guardrails and guidance, particularly if you want end users to be able to produce consistent and standardized visualizations without knowing anything about it.
A little bit more than that! Here shows why a higher-level abstraction can be helpful for chart generation: https://github.com/microsoft/flint-chart#features