Flint: A Visualization Language for the AI Era
11–20 of 81 posts
Re: Flint: A Visualization Language for the AI Era
#12If 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.
Re: Flint: A Visualization Language for the AI Era
#13Why 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?
Like you created you own framework for wen apps before.
"For the AI era" is the necessary buzzword
Re: Flint: A Visualization Language for the AI Era
#14Re: Flint: A Visualization Language for the AI Era
#15LLMs are surprisingly bad at generating JSON.
Re: Flint: A Visualization Language for the AI Era
#16unfortunately JSON is doomed to fail in "the AI era" LLMs are surprisingly bad at generating JSON.
Re: Flint: A Visualization Language for the AI Era
#17unfortunately JSON is doomed to fail in "the AI era" LLMs are surprisingly bad at generating JSON.
Re: Flint: A Visualization Language for the AI Era
#18Re: Flint: A Visualization Language for the AI Era
#19Re: Flint: A Visualization Language for the AI Era
#20Even in the Era AI, GGPlot's API is still the best charting API. The name "Grammar of Graphics" isn't just marketing, they literally sought to write a god damn grammar to was capable of expressing all possible qualitative graphics. They even wrote a book about how they went about it (not that it speaks to the quality of the API) https://link.springer.com/book/10.1007/0-387-28695-0 I actually stumbled upon this book w…