Flint visualization language
Ranked 6 of 19 charting libraries by recommenders
Free language that compiles compact chart definitions, praised for cutting formatting boilerplate; critics say it adds little over existing JSON chart specs.
Free language that compiles compact chart definitions, praised for cutting formatting boilerplate; critics say it adds little over existing JSON chart specs.
30 people gave an opinion
- recommend it
- 15
- criticize it
- 15
- approval share
- 50%
Recommended in 6 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: 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: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 15 people recommend itNeeds 10 or more, met.
- 1 recommender for every criticNeeds 2 to 1 or better, not met.
- Recommended in 6 of 13 monthsNeeds 4 or more, 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
Useful for LLM chart generation
“If the LLMs are better at generating Flint than Vega-Lite specs then I see how the project can be useful.”
Comment from 1 Aug 2026 in “Flint: A Visualization Language for the AI Era” “Flint is more reliable if you don't want to dedicate a whole skill to making charts”
Comment from 1 Aug 2026 in “Flint: A Visualization Language for the AI Era” “a higher-level abstraction can be helpful for chart generation”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” Compact encoding cuts formatting boilerplate
“Semantic types as the extra formatting factor is super useful because they are concise encodings of a lot of formatting boilerplate.”
Comment from 9 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “by moving some decisions to the compiler to reduce generation cost while maintain good expressivenss”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” Single native binary, no runtime
“compile it into a tiny 300KB native binary, and drop it on a production server without installing ANY runtime or dependencies”
Comment from 28 Mar 2026 in “Show HN: Flint – A compiled language to replace complex Bash scripts” “Don't need to install anything.”
Comment from 24 Oct 2026 in “OBS Studio 33”
What people warn about
Each mark is one comment
Adds little over existing JSON specs
“What is the point of this. I already can get an llm to draw charts”
Comment from 1 Aug 2026 in “Flint: A Visualization Language for the AI Era” “by no means are they an improvement over what I'd get”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “echarts already has a JSON co figuration spec”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” - Comment from 9 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents”
Hard to edit or read
“lacks some easy way to do alignments or grouping, which makes editing frustrating”
Comment from 9 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “a syntax also consumable by humans it is not!”
Comment from 8 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” Small audience, mostly toy projects
“either way the number of people willing or compelled to learn it will be tiny”
Comment from 9 Jul 2026 in “Show HN: Microsoft releases Flint, a visualization language for AI agents” “This can work only for toy projects with no complex build scripts”
Comment from 30 Aug 2026 in “Show HN: Flint – A minimal C/C++ package manager and build tool written in C”
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
31 of the 33 comments that mention it, newest first. Each links to the original comment.
“Wow. I'm rarely astounded by software these days. This is amazing.”
“Whoa, this is crazy good.”
“Don't need to install anything.”
“This can work only for toy projects with no complex build scripts”
“If the LLMs are better at generating Flint than Vega-Lite specs then I see how the project can be useful.”
“What is the point of this. I already can get an llm to draw charts”
“Feels to me like a preexisting project that pivoted their marketing pitch to AI.”
“I really don't see the point.”
“it's just a tool to create charts not a "visualization language"”
“Flint is more reliable if you don't want to dedicate a whole skill to making charts”
“It's cool...but is it needed?”
“This is a formal language that compiler can take!”
“Semantic types as the extra formatting factor is super useful because they are concise encodings of a lot of formatting boilerplate.”
“That's no language, that's a JSON schema”
“either way the number of people willing or compelled to learn it will be tiny”
“lacks some easy way to do alignments or grouping, which makes editing frustrating”
“It's a very powerful language but needs guardrails and guidance”
“this is an intermediate language designed to get 95% stuff right easily”
“a higher-level abstraction can be helpful for chart generation”
“going higher-level for abstractions, as is being argued for here, is strictly worse”
“Will anyone look at the slop charts? Of course not, the tokens are the goal.”
“by moving some decisions to the compiler to reduce generation cost while maintain good expressivenss”
“by no means are they an improvement over what I'd get”
“this project is a great example”
“echarts already has a JSON co figuration spec”
“a syntax also consumable by humans it is not!”
“compile it into a tiny 300KB native binary, and drop it on a production server without installing ANY runtime or dependencies”
“your current readme reads like AI generated.”
“your current readme reads like AI generated”
“to get rid of the slow edit-deploy-test loop when working with Go AWS Lambdas”
“file tools (converter, PDF organizer, metadata cleaner, subtitle tools)”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.