4 ms·

Thank you. It isn't hard to find, but my point was that if you say "using an intuitive declarative language" then a developer will get excited by a code snippe

by xrd 5y ago

Thank you. It isn't hard to find, but my point was that if you say "using an intuitive declarative language" then a developer will get excited by a code snippet that shows that intuitive developer language. It wasn't there, and I think their post could be improved by having less fluffy language and more code, if they are targeting me, that is. This link does show the code, but it took a few clicks to get there from your links: https://docs.dagger.io/1202/plan https://docs.dagger.io/1202/plan At first glance I'm not in love with the language. When I look at the first example, there is a lot I have questions about.

verdverm 5y ago
The language is CUE, which I think will see mass adoption in config / DevOps in the coming years. So regardless what you think of the language today, it is likely to become important and part of your like in the not too distant future. https://cuelang.org https://cuelang.org | https://cuetorials.com https://cuetorials.com Dagger builds on top of CUE and the (DAG) flow engine therein
- xrd 5y ago
  That's great context. That should be added to that doc link right at the top, it would have me feel much more safe about investing the time to learn it!
  - verdverm 5y ago
    CUE has good pedigree, the creator Marcel wrote the prototype for Borg (k8s), worked on both Google config languages, and worked on the Go team. CUE is how he thinks those Google config languages should have been designed.
- dijksterhuis 5y ago
  Oh wow, the validating yaml example on the front page looks super useful. Might try and play with this over the next few weeks!
  - verdverm 5y ago
    Once CUE clicked for me, there was no going back