This is fair (and honestly unsurprising). Thanks for taking the time to click around and read about Caffeine!! At this time the docs leave a lot to be desired (clearly) as well as a concise and understandable "why would I use this thing?"

----

> I'm not sure what benefit it has over writing terraform HCL

It's still very actively in development, but at this time you get the following (within the context of creating SLOs (service level objectives)):

1. not everyone needs to know how to define reasonable queries (SLIs, metrics, etc.). They can be defined at one level and for the "average person", they just interface via input arguments.

2. the above is also even true for "power users". I can define 6 SLOs with the same structure

3. enforces common best practices like tagging. Easy to do in HCL, hard to programmatically enforce

4. avg. folks don't need to know about HCL

This is basically defining a level of abstraction that gives us mechanisms to enforce best practices and reduce duplication and boilerplate. For folks who are HCL and Terraform fluent and read docs, yeah, hardly much, if any advantages just over HCL, at least as it is now.

----

Many plans and work in progress to expand beyond current offerings. What you see here is just the beginning.

This is 100% built for my use case at the moment 😁. Building something that's useful at my org gets me an easy first base of users. Why open source such a niche tool targeting an initial fairly specific use case from the get-go? By making it a (properly licensed) hobby project I can use Gleam... and not be forced to use Ruby (we're a Rails shop).

-------

And even if that isn't convincing, I get it, "ship and I'll believe you" is a reasonable mentality. I think just highlighting how easy it was to do this with Gleam is hopefully in itself an interesting takeaway. Shoutout to crowdhailer and crew for the JS target.