undefined | Better HN

0 pointsverdverm3y ago0 comments

You don't want computability in your config, and CUE is useful beyond APIs.

You can already use CUE within other programs when you need imperative, there is also the scripting layer where this is possible. There is also a plan to support a WASM runtime so you can have imperative subroutines in the scripting layer, written in any other language.

0 comments

mountainriver3y ago

My problem is generally the config is a part of a larger data model, which often needs to define imperative methods on resources. Having stuff in Cue means yet another layer and language I have to learn and use for this part of my API, and then copy that into a full API language.

verdvermOP3y ago

How are you defining that model and methods today? Are they already in the tech / lang you use or are you using some translation like protobuf or openapi?

(curiosity as I'm building a tool on top of CUE that combines it with notions of data models and code gen, and I'm always keen to learn more about the things people do today)

j / k navigate · click thread line to collapse

0 comments

mountainriver3y ago

verdvermOP3y ago

How are you defining that model and methods today? Are they already in the tech / lang you use or are you using some translation like protobuf or openapi?

(curiosity as I'm building a tool on top of CUE that combines it with notions of data models and code gen, and I'm always keen to learn more about the things people do today)

j / k navigate · click thread line to collapse