starlark-rust VS cue

Compare starlark-rust vs cue and see what are their differences.

starlark-rust

A Rust implementation of the Starlark language (by facebook)

cue

CUE has moved to https://github.com/cue-lang/cue (by cuelang)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
starlark-rust cue
9 28
603 3,181
6.8% -
9.8 9.1
7 days ago over 2 years ago
Rust Go
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

starlark-rust

Posts with mentions or reviews of starlark-rust. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-04.

cue

Posts with mentions or reviews of cue. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-17.
  • The Perfect Configuration Format? Try TypeScript
    17 projects | news.ycombinator.com | 17 Nov 2021
  • YAML: It's Time to Move On
    29 projects | news.ycombinator.com | 14 Nov 2021
  • Ask HN: What you up to? (Who doesn't want to be hired?)
    25 projects | news.ycombinator.com | 1 Nov 2021
    I'm continuing to work on https://concise-encoding.org which is a new security-conscious ad-hoc encoding format to replace JSON/XML and friends. I've been at it for 3 years so far and am close to a release.

    In a nutshell:

    - Edit in text, transmit in binary. One can be seamlessly converted to the other, but binary is far more efficient for processing, storage and transmission, while text is better for humans to read and edit (which happens far less often than the other things).

    - Secure by design: Everything is tightly specced and accounted for so that there aren't differences between implementations that can be exploited to compromise your system. https://github.com/kstenerud/concise-encoding/blob/master/ce...

    - Real type support because coercing everything into strings sucks (and is another security risk and source of incompatibilities).

    XML had a good run but was replaced by JSON which was a big improvement. JSON also had a good run but it's time for it to retire now that the landscape has changed even further: Security and efficiency are the desires of today, and JSON provides neither.

    I've got the spec nailed down and can finally see the light at the end of the tunnel for the reference implementation in golang. I still need to come up with a system for schemas, but I'm hoping that https://cuelang.org will fit the bill.

  • No YAML
    6 projects | news.ycombinator.com | 27 Oct 2021
    Has anyone taken a look at Cue who can share any experiences?

    https://cuelang.org/

    It's mentioned on the site as an alternative to Yaml. Recently watched (~half of) this intro to it: https://youtu.be/fR_yApIf6jU

  • Cue: A new language for data validation
    17 projects | news.ycombinator.com | 19 Oct 2021
    the most interesting summary explanation of cue lang and its differences is from a bug filing - https://github.com/cuelang/cue/issues/33

    >CUE is a bit different from the languages used in linguistics and more tailored to the general configuration issue as we've seen it at Google. But under the hood it adheres strictly to the concepts and principles of these approaches and we have been careful not to make the same mistakes made in BCL (which then were copied in all its offshoots). It also means that CUE can benefit from 30 years of research on this topic. For instance, under the hood, CUE uses a first-order unification algorithm, allowing us to build template extractors based on anti-unification (see issue #7 and #15), something that is not very meaningful or even possible with languages like BCL and Jsonnet.

    17 projects | news.ycombinator.com | 19 Oct 2021
  • CMake proposal: Unified way of describing dependencies of a project
    2 projects | /r/cpp | 5 Oct 2021
    I agree with you. Personally, I think Cue is much better than either YAML, TOML or JSON because it adds the concept of types to the idea of describing configuration.
  • Cloud Infrastructure as SQL
    9 projects | news.ycombinator.com | 16 Sep 2021
    true, but the tooling and workflow remains the same.

    Not sure of any tool that could abstract the details sufficiently to be widely adopted. There is just too much nuance in cloud config.

    I'm exploring using CUE (https://cuelang.org) to define TF resources, exporting as JSON for TF. So far it's much nicer

  • Ask HN: What open source projects are you working on and why?
    7 projects | news.ycombinator.com | 8 Sep 2021
  • Tgen: A template tool a la Helm or Consul Templates
    4 projects | news.ycombinator.com | 3 Sep 2021
    I've been using https://cuelang.org for any configuration / yaml like generation. This link has a GH search with two discussions that talk about Rego: https://github.com/cue-lang/cue/search?q=rego&type=discussio...

    I wrote https://github.com/hofstadter-io/hof to use this concept "at scale", i.e. inputting & outputting multiple files & dirs. The main idea was to generate common code across the stack from a single-source-of-truth. Today it inputs CUE only, which has all the things needed to validate the incoming data and also contains the templates, so `hof gen` takes the same args as `cue export`. It uses diff3 so that you can regenerate the output after modifying the input or the generated content, which is something I needed so that when I fill in the generated API handler func, and then change the design a bit, that I can keep the manual work.

What are some alternatives?

When comparing starlark-rust and cue you can also consider the following projects:

terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.

dhall-lang - Maintainable configuration files

jsonnet - Jsonnet - The data templating language

Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀

ytt - YAML templating tool that works on YAML structure instead of text

cue - The home of the CUE language! Validate and define text-based and dynamic configuration

yamllint - A linter for YAML files.

yaml - YAML support for the Go language.

.tmux - 🇫🇷 Oh my tmux! My self-contained, pretty & versatile tmux configuration made with ❤️

starlark-go - Starlark in Go: the Starlark configuration language, implemented in Go

yaml-rust - A pure rust YAML implementation.

terraform-lsp - Language Server Protocol for Terraform