How CUE Wins (2021)

#1

Post by ahamez » Fri, Jan 13, 2023, 2:09 PM UTC

How CUE Wins (2021)
blog.cedriccharly.com

Re: How CUE Wins (2021)

#2

Post by Kinrany » Fri, Jan 13, 2023, 2:51 PM UTC

I think CUE looks great, but right now it's losing because it can only be installed as a package for Go, MacOS and Arch.

Re: How CUE Wins (2021)

#3

Post by 4ad » Fri, Jan 13, 2023, 3:06 PM UTC

Kinrany wrote: post #2

I think CUE looks great, but right now it's losing because it can only be installed as a package for Go, MacOS and Arch.

The CUE command line tool is written in Go, and works on pretty much any operating system and architecture supported by Go, which now includes almost everything[0], so I am not sure how you came to that conclusion.

If you want to use CUE as a library, you can only do it from Go at the moment. We are acutely aware of this limitation and we are investigating possible solutions.

[0] https://go.dev/doc/install/source#environment

Re: How CUE Wins (2021)

#4

Post by jjtheblunt » Fri, Jan 13, 2023, 3:07 PM UTC

What is CUE? (The article seems to presume familiarity?). Edit: browser coloring settings stupidity on my end: thanks to commenter below.

Re: How CUE Wins (2021)

#5

Post by lokar » Fri, Jan 13, 2023, 3:10 PM UTC

4ad wrote: post #3

Kinrany wrote: post #2

I think CUE looks great, but right now it's losing because it can only be installed as a package for Go, MacOS and Arch.

The CUE command line tool is written in Go, and works on pretty much any operating system and architecture supported by Go, which now includes almost everything[0], so I am not sure how you came to that conclusion. If you want to use CUE as a library, you can only do it from Go at the moment. We are acutely aware of this limitation and we are investigating possible solutions. [0] https://go.dev/doc/install/source#env…

Also, the docs need a lot of work

Re: How CUE Wins (2021)

#6

Post by chriswarbo » Fri, Jan 13, 2023, 3:10 PM UTC

Kinrany wrote: post #2

I think CUE looks great, but right now it's losing because it can only be installed as a package for Go, MacOS and Arch.

It's in Nixpkgs, so you can use it anywhere that's supported (any Linux distro, macOS, WSL, etc.)

Re: How CUE Wins (2021)

#7

Post by selbyk » Fri, Jan 13, 2023, 3:11 PM UTC

jjtheblunt wrote: post #4

What is CUE? (The article seems to presume familiarity?). Edit: browser coloring settings stupidity on my end: thanks to commenter below.

There is a link to a page about it in the second paragraph

Re: How CUE Wins (2021)

#8

Post by chriswarbo » Fri, Jan 13, 2023, 3:13 PM UTC

I've been gradually introducing CUE at my workplace. So far I've used it to generate AWS CloudFormation templates, GitHub Actions workflows, and OCI container configs. I'm also using it in git pre-commit hooks to validate files against existing jsonschemas.

Re: How CUE Wins (2021)

#9

Post by 4ad » Fri, Jan 13, 2023, 3:14 PM UTC

lokar wrote: post #5

4ad wrote: post #3

Earlier quoted context omitted.

The CUE command line tool is written in Go, and works on pretty much any operating system and architecture supported by Go, which now includes almost everything[0], so I am not sure how you came to that conclusion. If you want to use CUE as a library, you can only do it from Go at the moment. We are acutely aware of this limitation and we are investigating possible solutions. [0] https://go.dev/doc/install/source#env…

Also, the docs need a lot of work

We are painfully aware of this, we are rewriting and improving the documentation as we speak and we are also working on a new web site.

Re: How CUE Wins (2021)

#10

Post by Existenceblinks » Fri, Jan 13, 2023, 3:14 PM UTC

I try to find what's the definition of "wins" and looking for some mass use case by which companies. "wins" in this article seems to be "I think this is good", am I missing something?