Why is this "for the AI era"? Isn't it kind of not for the AI era since an LLM can create a gnarly python or js chart of whatever you want in seconds?

Maybe they’re not selling this well. Maybe they’re so close to the AI research that this seems like an obviously good idea.

But there’s not one word of why this is good for LLMs, or how they tested/measured that.

My gut would tell me that a new solution put up against all the vega lite specs it’s already be trained on would be a hard thing to win.

This needs a side-by-side config comparison with something like echarts config schema format. I really don't see the point.

I'm 99% sure the verbosity required in the system prompt to teach non-M$ models this new ever-so-slightly-different-but-not-obviously-necessary chart def abstraction format, and the iterations required to get it right, will outweigh any supposed efficiency gains resulting from using it.

Just stating the obvious.

What is the point of this. I already can get an llm to draw charts using plotly, matplotlib, echarts, etc all the time. There will be always a better way but what does this buy us?

This is just json right? One issue with llms right now it's that if you give them a json specification, they're not always amazing at following it. I think it makes sense to have an agent tool that takes llm json, a file name and a spec path and only writes out the file if it conforms.

If it's made for LLMs, the spec should be yaml not json. Way more token efficient

Every time I needed to do charts at work I had a conundrum. Libraries are aplenty but basically only plotly does everything, but it’s not the prettiest. I’d much rather developers contributed new features into existing libraries.

I've seen this play out plenty of times

Yeah this is not needed and every single day it is needed even less.