# CUE 29 Hacker News commenters recommended CUE and 7 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months. It meets the Hacker Approved badge rule. **Verdict:** People recommend CUE for unifying data and schemas in configs while staying declarative rather than Turing-complete. Critics say it is hard to learn and that its tooling and docs are still immature. ## Why people recommend it - Works with existing formats and tools (4 comments): "its ability to easily consume existing formats and export back to them, so upstream and downstream tools and workflows don't need to change" ([source](https://news.ycombinator.com/item?id=45781010)) "I'm using CUE in front of TF & k8s, in part because I have workloads that need a bit of both and share config" ([source](https://news.ycombinator.com/item?id=45903033)) "CUE works with all of those languages, so it doesn't matter what the tools or others are using." ([source](https://news.ycombinator.com/item?id=46673157)) - Declarative without being Turing-complete (3 comments): "CUE strikes a really nice balance between being primarily data description and not a Turing-complete language" ([source](https://news.ycombinator.com/item?id=46264082)) "I've moved to CUE instead of a general purpose PL, to remain in the declarative space." ([source](https://news.ycombinator.com/item?id=47544147)) "It seems like it's really solving the 'code as configuration' problem properly" ([source](https://news.ycombinator.com/item?id=46652894)) - Strong schema enforcement and validation (4 comments): "I like CUE a lot. We use it pretty heavily for schema enforcement of CRDs." ([source](https://news.ycombinator.com/item?id=46647326)) "it is the only one that lets you write schemas for arbitrary refinements" ([source](https://news.ycombinator.com/item?id=48982627)) "which allows you to do first-class version compatibility modelling" ([source](https://news.ycombinator.com/item?id=46954485)) - Simple yet powerful unification model (2 comments): "unification is very intuitive and whole model is one of the best (formalized!) ideas at _simplifying_ configs" ([source](https://news.ycombinator.com/item?id=46647678)) "it's a really cool idea, one of those things that's simple enough to be intuitive but also really powerful" ([source](https://news.ycombinator.com/item?id=46275782)) ## What people warn about - Hard to learn and syntactically awkward (3 comments): "it looked like it was too syntactically complex and unwieldy for them to edit" ([source](https://news.ycombinator.com/item?id=46646907)) "the number one complaint from our early users was having to learn CUE" ([source](https://news.ycombinator.com/item?id=46265956)) "the language seems pretty awkward and hard to understand" ([source](https://news.ycombinator.com/item?id=46653841)) - Immature tooling and thin docs (3 comments): "the tooling just isn't there for much of what I need yet" ([source](https://news.ycombinator.com/item?id=45903089)) "I'd say cue is nicer, but the tooling available is even less mature." ([source](https://news.ycombinator.com/item?id=48244272)) "the docs and some of the libraries were a bit lacking" ([source](https://news.ycombinator.com/item?id=49185644)) - Overkill or inflexible for small setups (2 comments): "using CUE absolutely does not make sense at a small scale; just write your YAML" ([source](https://news.ycombinator.com/item?id=46278142)) "the loss of flexibility within a special-purpose language like CUE is enough for people to ask why not just bother writing the scripts" ([source](https://news.ycombinator.com/item?id=46645492)) ## Alternatives hackers recommend - [TOML](https://hackerapproved.com/p/toml.md): 19 recommend - [Jsonnet](https://hackerapproved.com/p/jsonnet.md): 12 recommend - [HCL](https://hackerapproved.com/p/hcl.md): 10 recommend - [Dhall](https://hackerapproved.com/p/dhall.md): 9 recommend - [Nickel configuration language](https://hackerapproved.com/p/nickel.md): 8 recommend ## Cite as Hacker Approved, "CUE", https://hackerapproved.com/p/cue/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).