CUE
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
4recommend
0warn against
Jan 16, 2026first mention
Oct 30, 2026latest mention
Why people recommend it
“I use CUE as the deterministic abstraction layer and generate Go/TS from that”
“MVS + OCI is the gold standard imo”
Show 3 more
“It's the best thing I've come across (that I don't need to mange myself)”
“They are central to my personal dev tool”
“This is where configuration language like CUE can be used to complement LLM [1].”
Caveats and dissent
No one in these comments warned against it.
Often compared with
Threads where it came up
- Ask HN: What's missing for a true deterministic abstraction layer? 1 mention
- Don't couple your Go code to GitHub 1 mention
- Ask HN: How do you manage skills files? 1 mention
- Ask HN: What dev tools do you rely on that nobody talks about? 1 mention
- 100 hour gap between a vibecoded prototype and a working product 1 mention
- I'm going to build my own OpenClaw, with blackjack and bun 1 mention
Data: cue.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 7
“I use CUE as the deterministic abstraction layer and generate Go/TS from that”
“MVS + OCI is the gold standard imo”
“It's the best thing I've come across (that I don't need to mange myself)”
“They are central to my personal dev tool”
“This is where configuration language like CUE can be used to complement LLM [1].”
“My stack is built on ADK-go, CUE, Dagger, VSCode, and system prompts derived from Claude Code”
“I like CUE a lot. We use it pretty heavily for schema enforcement of CRDs.”