Live data from Hacker News

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

cuelang.org

21–30 of 167 posts

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

#21
post #13

my time at Google has made me hate GCL so much.

I was going to say, this looks a lot like GCL. Dynamic scope, recursive lookup in parent scopes, templates [1], everything. GCL is neat and all, but I'd almost rather write my job configs by building thin python or lisp scripts to emit json or protos.

1: https://github.com/cuelang/cue/blob/master/doc/tutorial/basi...

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

#23
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!

Even worse, the examples are complex and incomplete.

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

#24
Ill prolly get downvoted for this:

What i want to see, is a company which will provide as a service, basically devops deployment, monitoring and provisioning regardless of the cloud provider.

Such that i can say “deploy this” and it will eval, track and monitor the cost of the deployment across aws, azure, gcp, etc and i can click controls to see/kil/scale wherever...

Thus, i dont care about cloud provider deployment language, etc...

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

#25

Here is an interesting example showing what it looks like: https://github.com/cuelang/cue/blob/e5d8d09b3ba2e4f48c84a3b5... I used the following command on the cloned repository to find it[1]: find . -iname '*.cue' | xargs ls -l | tr -s ' ' | cut -d ' ' -f5,9 | sort -n [1] Note that 'find' has a '-printf' option which could have been used to simplify this one-liner.

Or just search the files directly in github? Just type T and .cue

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

#27
post #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.

Worst case scenario it has a short life and is forgotten for a better OSS alternative but remains the default for several Google projects and a number of developers are forced to learn and maintain it as it becomes brittle with age.

With that as the worst case scenario, it's more than worth the try.

Post reply on HN