Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Why do ppl think building something through yaml is ever a good idea??

    (I know why: for a platform it’s simpler to parse a yaml than to run code, but it’s almost never a good idea for anything that needs to scale in complexity)

  • DAC currently supports YAML and JSX, what else would be a good alternative?
  • What is a better format that allows inline comments, is human readable, and can be easily converted to other formats (json, xml, et al)
  • I would really hesitate to use a 1000 lines of yaml and modify them. I never found YAML easy to modify after a certain size.
  • You have trouble with them when you are modifying them by hand or using an LLM to do it? The purpose of this project is having LLMs do it. I found they are about as good at writing yaml as they are writing anything else.
  • Have you thought about how these dashboards could be built for an eink screen?

    For a while, I was thinking about starting a side project of selling E-ink screens with easily configured dashboards. The project would support hobbies who want to build dashboards powered by a raspberry pi or something. I never pursued it, but it seems like you are now halfway there.

  • What I’ve heard often is that the customer might want to build a dashboard using AI on the fly.

    Like imagine you have a site and there’s blank canvas. It has access to some data in the background. The user might be like “build a dashboard showing YoY performance of X and break down the shipments in a table by Y and Z”. Then the agent builds it and persists it such that when they log out and log back in they can see their custom dashboard they assembled themselves.

  • I reckon this is a simplification of existing BIAC tools (eg, https://github.com/lightdash/lightdash)
  • Partly, yes. It is a simplification with the perspective that the agents would be the primary builders.
  • Love the idea. The ability to PR a dashboard would've helped us in multiple companies.

    The two big areas that could use some docs/work: - Auth (one company was healthtech, so we needed auth even on VPN. The other didn't have a VPN so we needed auth) - Hosting: If it just needs to be run in a container and it doesn't need to be restarted that's fine. Though if there isn't a hosting document it's often a sign of a service that will need someone to keep it running all the time

  • Well done on the launch! We’ve doubled down on the apps as YAML paradigm a few years ago and its pay great dividends on all fronts, esp now with code gen spinning out apps faster than ever for us (generated yaml). Our largest app is well over 500k lines of yaml - for those complaining about 1000 lines lol. With the right tool stack and conventions its so much easier to read, write. review and maintain. Shameless plug, we’ve built Lowdefy (open source) and 100s of dashboards using it. Have a look and keen to unpack if you’re interested in sharing experiences. Specially have a look at what we did with operators for dynamic needs. https://github.com/lowdefy/lowdefy
  • Consider adding that snazzy gif in the README to the docs landing page. I went straight to the docs and then hunted for a screenshot to no avail.
    by lexh
  • That's a great idea, will do very quickly, thanks!
  • DaC might be more distinguishable from DAC, although the context obviously also helps readers telling them apart.

    Yours sincerely, came here for another DAC

    by 5-0
  • Point taken, thanks! Out of curiosity, which DAC did you come here for?
  • Why not use Vega-Lite[0]? It’s my go-to data viz DSL with Claude.

    [0] https://vega.github.io/vega-lite/

  • Observable Framework[0] attempted to fill this niche for a while as well, and we'll likely see some of the implementation details in the new Observable Notebook 2.0 format too.

    [0]: https://github.com/observablehq/framework

  • There are quite a few libraries for charts and visualization, there are not as many for actually combining many of them with layouts, different components and including the actual implementation of the backend. Dac aims to provide all that as a standard and an implementation.
  • Might want to add how this compares to other products in the space.

    Some that come to mind that are potentially tangentially related/similar:

    https://github.com/evidence-dev/evidence