Flint visualization language by Microsoft
Shares rank 8 of 19 charting libraries by recommenders
Recommended as a simple, compact JSON spec that lets AI agents and people generate polished charts from short specs. Critics question its JSON-based design and whether it is better than existing chart APIs.
Recommended as a simple, compact JSON spec that lets AI agents and people generate polished charts from short specs. Critics question its JSON-based design and whether it is better than existing chart APIs.
21 people gave an opinion
- recommend it
- 11
- criticize it
- 10
- approval share
- 52%
Recommended in 2 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 11 people recommend itNeeds 10 or more, met.
- 1.1 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 2 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Simpler, shorter spec than chart APIs
“The intention here is that Flint is a simpler abstraction to get basic setups right and any followup edits can be done on top of the first compiled outputs”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “the generated spec can be easy for user to edit since there is no need for hard-coded low-level parameters”
Comment from 9 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “The idea is that you don't have to fill position / axes details just to make the chart work.”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” - Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents”
- Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents”
Polished charts with little iteration
“Flint has advantage of being an intermediate language that allow agents to generate good-looking stuff without additional refinement loops”
Comment from 9 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “Functions extremely well and the result is a very clear (and consitent) human-readable "output layer."”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “Flint lets you get there in 20 second with 200 tokens with a 95% polished chart”
Comment from 9 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” - Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents”
Easy for LLMs to generate
“This is a valuable method of closing the gap in making LLM results available in a good visual form.”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “an easy-to-generate language for expressing charts. That's impressive! That's useful.”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” Easy to switch and edit charts
“Being able to easily switch between "ECharts Sunburst" and "Vega-Lite faceted bar" seems like a super useful ability.”
Comment from 1 Aug 2026 in “Flint: A Visualization Language for the AI Era” “the generated spec can be easy for user to edit since there is no need for hard-coded low-level parameters”
Comment from 9 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents”
What people warn about
Each mark is one comment
Stringly typed JSON design
“Flint being stringly typed in JSON is a decision that I don't think I agree with”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “Expressing charts in XML, JSON, etc is a terrible idea.”
Comment from 9 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “a stringly typed JSON-based DSL without a linter or LSP”
Comment from 1 Aug 2026 in “Flint: A Visualization Language for the AI Era” Not clearly better than chart APIs
“How is this specific to the marketed AI integration? This could just be a unifying abstraction layer for a bunch of, in my opinion, verbose chart APIs.”
Comment from 1 Aug 2026 in “Flint: A Visualization Language for the AI Era” “This is DOA honestly and not really better than what we had before.”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” Unclear purpose and weak AI focus
“The linked website has only two mentions of AI, and one of them is the title”
Comment from 1 Aug 2026 in “Flint: A Visualization Language for the AI Era” “I don't really understand the point of this”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents”
Other charting libraries people recommend
The four most recommended other charting libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 19 charting libraries, rankedWhat people said
28 of the 29 comments that mention it, newest first. Each links to the original comment.
“The linked website has only two mentions of AI, and one of them is the title”
“it seems to be working just fine!”
“What a waste of time over at Microsoft Research”
“Microsoft will have abandoned it for some other shiny buzzword”
“How is this specific to the marketed AI integration? This could just be a unifying abstraction layer for a bunch of, in my opinion, verbose chart APIs.”
“I trust my setup a lot more than whatever this is.”
“Being able to easily switch between "ECharts Sunburst" and "Vega-Lite faceted bar" seems like a super useful ability.”
“a stringly typed JSON-based DSL without a linter or LSP”
“Flint has advantage of being an intermediate language that allow agents to generate good-looking stuff without additional refinement loops”
“Expressing charts in XML, JSON, etc is a terrible idea.”
“It's machine friendly but not exactly LLM friendly.”
“the generated spec can be easy for user to edit since there is no need for hard-coded low-level parameters”
“Flint lets you get there in 20 second with 200 tokens with a 95% polished chart”
“This is a valuable method of closing the gap in making LLM results available in a good visual form.”
“it is quite nice to see that even the Microsoft dinosaur gets it”
“Flint uses semantic type and a layout optimization algorithm to handle this”
“This is DOA honestly and not really better than what we had before.”
“I do find the chartType part is not quite elegant, since templates should be more extensible.”
“Flint being stringly typed in JSON is a decision that I don't think I agree with”
“I don't really understand the point of this”
“The intention here is that Flint is a simpler abstraction to get basic setups right and any followup edits can be done on top of the first compiled outputs”
“an easy-to-generate language for expressing charts. That's impressive! That's useful.”
“Flint is a higher-level abstraction, with simpler much shorter spec”
“This is fun! We started thinking it would just be an engineering task in the beginning”
“Functions extremely well and the result is a very clear (and consitent) human-readable "output layer."”
“this DSL is better even for humans”
“This is cool to see from a research team.”
“The idea is that you don't have to fill position / axes details just to make the chart work.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.