Live data from Hacker News

Cue – A language for defining, generating, and validating data

cuelang.org

1–10 of 167 posts

Re: Cue – A language for defining, generating, and validating data

#6

The tl;dr is buried deep in the docs > CUE is an extension of JSON. This improves familiarity and makes it easy to get going quickly. > In its simplest use case, CUE can substitute for a more pleasant way to write JSON.

So it’s a google branded yaml?

Let’s raise a glass to our blue eyed comrades who’ll adopt this fully, only for google to decide in 2-3 years to completely and aggressively kill it again for no apparent reason.

Re: Cue – A language for defining, generating, and validating data

#7
post #3

Seems like an interesting language, but I'm very disappointed that my first attempt to view example code took 5 clicks. The most important part of any programming language website is a short example snippet: put it above the fold on the front page!

I didn't even have to scroll down to see an example of code and usage.

Re: Cue – A language for defining, generating, and validating data

#8
Very interesting, I can think of a lot of places where this would be useful for managing infrastructure.

I highly recommend reading about some of the internals, it is making me rethink a lot of how configuration should be done.

https://cuelang.org/docs/concepts/logic/

Re: Cue – A language for defining, generating, and validating data

#9
post #3

Seems like an interesting language, but I'm very disappointed that my first attempt to view example code took 5 clicks. The most important part of any programming language website is a short example snippet: put it above the fold on the front page!

I didn't even have to scroll down to see an example of code and usage.

Where? I don't see any example on the page linked to.

Edit: Ah, the code example only appears for desktop browsers (or at least, browser windows wider than a phone screen).

Re: Cue – A language for defining, generating, and validating data

#10
Seems really interesting after a quick read-through. Specs that allow range-based validation look useful, and the structural declarations also feel like they'll help reduce a lot of boilerplate and repetition. I wonder how this compares with Dhall and Jsonnet, both of which I've been looking into as a safer alternative to templated YAML. With Google putting its weight behind this I'm curious if it'll start finding its way into K8s.
Post reply on HN