So this is one interface that can render to multiple charting backends?
If AI is writing the "Flint", why not just have it write the backend code instead? I'm not sure why I would want pluggable charting backends.
I can see an argument for providing simpler APIs for LLMs, though, so that it can be more token efficient for example.
Different charting backends support different kinds of charts. Being able to easily switch between "ECharts Sunburst" and "Vega-Lite faceted bar" - one of the examples on the project website - seems like a super useful ability.