Live data from Hacker News

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

cuelang.org

121–130 of 167 posts

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

#121
post #19

Earlier quoted context omitted.

Pardon for slamming my ignorance down on the table here: I know Google has a tendency of killing products but I’m not familiar with many of their engineering tooling being similarly sunset with comparable frequency. Any named examples? I’m sure there are-and likely they just elude me at present, maybe seeing their names will jog the memory probably?

jsonnet? :)

The jsonnet mailing list still has activity. Is the project dead?

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

#122
post #79

Cute. Is there something that takes in Cue and makes a GUI editor for the format?

Wouldn't the optimal one be a mode for your editor of choice?

I mean a form, with blanks and pulldowns. There's enough info in Cue to generate one. Not just a syntax checker that tells you that you got it wrong.

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

#123

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…

checkout https://apex.sh/up/

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

#124
post #101
post #78

Earlier quoted context omitted.

I realize this was meant to be sarcastic. However, I whole-heartedly and unironically agree. For writing small bits of configuration, just about any language will be fine. For large amounts of configuration, as is required for... oh, I dunno, let's say deploying software in the cloud, all the commonly used languages are a disaster. Data serialization languages (like JSON, INI, XML, etc) lack the power to describe lar…

I wholeheartedly and in ironically disagree! We have all we need. If you want a full featured language, use that. Beyond that, we have JSON, YAML, INI and more. If you want something more complicated you can create your own DSL for your app. If you want schemas and validation, use XML!

each of those options have major downsides:

- 'dumb data' (json, yaml, ...) is machine-, but not human-friendly. it's often tedious to write/read, and you can't abstract common parts out

- DSLs are something you have to write, debug and maintain yourself. is the bug in your config or is it in your DSL's implementation? who knows!

- full featured languages require a full blown interpreter and aren't tooling-friendly. as an example: with a Python package, it's not really possible to statically determine the dependencies , because its setup.py can declare anything it pleases depending on, say, the time of day. also you can't really run untrusted configs because they might launch some missiles

---

there's a decent middle ground – write a program that generates a 'dumb data' config. you write a small amount of code (friendly for humans) and run it to get a static, easy-to-process config (friendly for machines). however in practice (in most languages) the program won't be pretty – probably about as easy to read/write as an implementation of a macro that directly manipulates ASTs (i.e. not very). this can sometimes be ameliorated with some EDSL trickery, but that brings back all the problems DSLs have

and so generating configs is what projects like Dhall/Cue aim to improve. i'd say they're aiming to be something like the regex of config generation - do a limited amount of common&useful things, and make them easy to express.

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

#125
post #115
post #97

Earlier quoted context omitted.

Stop commenting on every HN post, thanks

Fact: I've commented on fewer than 1% of HN posts today alone. Fact: my post is very relevant to the OP and I'm offering to help them. Fact: I've been a member of this site for over 12 years, and never comment on a post unless I think it adds value to the discussion or would be helper to the parent.

FWIW I think your post is very relevant.

I like the idea of a git based database. Please don't take a single person's opinion as that of the entire community.

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

#127
post #86

I'm feeling both really pissed and validated right now. I thought this was going to just be a normal thoughtless config language that would only be successful as a Google project. Then I looked at the theoretical basis page. I have no formal proof about this, but I've been talking about this type of a type system with my parents and high school CS teacher for a while now! My idea sounds like this: a value is simply a…

Why feeling pissed? It is unlikely this Cue project implements the very same semantics the way you think about them. I'd go ahead and just write that paper. Looking forward seeing your reference implementation :-).

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

#128
post #37
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!

Well at least you could find an example. I couldn't find anything after like a minute of searching. Unless we're counting the gif that slowly shows you an example project letter by letter.

Someone please link to the code.

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

#129
I think a better title would be "Cue: A constraint programming langue (from some people who work[ed] at Google)".

When you consider the use of this language within a distributed system it's pretty freaking brilliant. https://cuelang.org/docs/concepts/logic/#the-value-lattice

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

#130

Earlier quoted context omitted.

Wouldn't the optimal one be a mode for your editor of choice?

I mean a form, with blanks and pulldowns. There's enough info in Cue to generate one. Not just a syntax checker that tells you that you got it wrong.

I don't think a gui to work with cue files is a good substitute for a gui for regular users to configure whatever you are configuring because its unlikely to be able to define valid data to the same degree as an actual app.

If its for a technical individual to configure your software I don't know that such a gui would be superior to your favorite editor.

Post reply on HN