Three prevalent themes in the discussion
- AI‑assisted, reproducible dashboard creation – Many commenters see dbt Charts as a way to let agents generate dashboards that are auditable, deterministic, and easy to version‑control.
- “Unbundling BI is absolutely where things are headed now that more people have agents, coding agents, agent computers to help with work.” – nzoschke
- “A beacon of hope between all the vibe coded JS slop charts and dashboards! I love that this creates artifacts that are readable, maintainable and reproduce the same dashboard consistently (deterministically!).” – mollifier14
-
“We hope this language + AI help make the BI space more open with dashboards as concise auditable code.” – thingsilearned
-
Desire for an open, shared charting language to avoid vendor lock‑in – Participants repeatedly stress the value of a standardized spec that different tools and agents can consume, promoting interoperability.
- “Congrats on the launch Dave! I was wondering who was going to launch an attempt at industry standard here.” – mceoin
- “Agreed. Coupled with bento for slide decks, I think this type of project is a very welcome development, helping us move away from walled gardens and proprietary software suites.” – stackghost
-
“if there was a unified spec that was agreed upon these third‑party harnesses and apps would all speak the same charting language which would be super cool.” – engrav3er40
-
Skepticism about using YAML as a DSL and questions about novelty – Some users argue that YAML is ill‑suited for logic, that the approach isn’t radically new, and that maintainability could suffer as the spec grows.
- “repeat after me: yaml is not a programming language. conditionals and variable binding become insane war crimes when yaml comes to town.” – carterschonwald
- “It's neat but pretends to be more innovative than it actually is. BI has already been decoupled from everything else. YAML/XML/JSON - that doesn't matter.” – dgudkov
- “AI can generate reusable artifacts … but what to do with that artifact afterwards? If you want it to be reusable it needs to be a well‑defined structured protocol/language.” – mollifier14