muze

id/our-approach/#principles/tabl...) alongside the design and architecture of the grid (open closed system + data flow + relinquishing right control to agents). Thus enforcing enough abstraction for agents that produce fewer bugs in a single shot (https://www.superplot.dev/grid/our-approach/#principles/head...). How is it different from a lib built for devs? Unlike a lib built for devs where the abstaction layer is much closer to humans (config driven like highcharts / aggrid), I belive having a different layer of abstraction from carefully defined building blocks and stable contracts help agents build reliable and stable outputs. For majority of the usecases, a user can ask an agent to build a particular representation of the grid (without waiting for the library to support it internally) to their liking. The agent would then go and build the grid with given constructs acting as guardrails. (Ofcourse there is a limit to that, for example if you want to do something which is outside the scope of mental model) What does it support? - Headless grid with virtualization - Local in browser datasource via duckdbwasm (supports pivot / tree / grouped data ops) - External datasource connection via our IR (codegen to db / semantic model should be easy given llm like structures) - Pivot + tree view + grouped data view - Table algebra support (that gets translated to IR for external datasource, for which agent can do codegen) - Pagination / data evictions for billions of row handling - Metadata plumbing (for usecases like complex cells where data needs to be generated from multiple differnet parameters) - Usage patterns / documentations (we are working on this) Some demos: https://www.superplot.dev/grid/#demos Github: https://github.com/superplothq/grid Would love to get your feedback on the approach as I continue to build the library.

e. With Muze, all charts rendered from the same DataModel are automatically connected (enabling cross-filtering). - Muze allows faceting of data out of box with multi-grid layout. - Composability of visualizations allow you to create any kind of cartesian visualization with Muze, without having to wait for the charting library vendor to release it as a ‘new chart type’ - Muze exposes Developer-first API for enabling interactivity and customizations. You can use the low-level API to create complex interaction We’ve literally just launched this last month or so, so I’d love some feedback if you can spare the time. Thanks for taking a look! Website: https://www.charts.com/muze Github: https://github.com/chartshq/muze