cue VS starlark-go

Where `kube.cue` sets reasonable defaults (e.g. image is /). The "cluster" runs on a mini PC in my basement, and I have a small Digital Ocean VM with a static IP acting as an ingress (networking via Tailscale). Backups to cloud storage with restic, alerting/monitoring with Prometheus/Grafana, Caddy/Tailscale for local ingress.

[1] https://www.talos.dev/

[2] https://cuelang.org/

I've been somewhat surprised that CUE bills itself as "tooling friendly" and doesn't yet have a language server- the number one bit of tooling most devs use for a particular language.

I'm assuming it's becaus CUE is still unstable?

Anyway, if others are interested in CUE's LSP work, I think https://github.com/cue-lang/cue/issues/142 is the issue to subscribe to

This is where I usually pitch in with "Have your heard of CUELang, our lord and savior?": https://cuelang.org/

- Not turing complete

CUE: The core problem CUE solves is "type checking", which is mainly used in configuration constraint verification scenarios and simple cloud native configuration scenarios.

If you really want executable configurations please consider a newer language like https://dascript.org or https://cuelang.org which provide better type safety.

1- https://news.ycombinator.com/item?id=38030778

Markdown and XML are nice, but what about more advanced documentation formats like OpenAPI? For one recent project, I set up automatic generation of the OpenAPI docs from (much more compact and flexible) CUE definitions (https://cuelang.org/) - which has the bonus of also being able to test the API against the definitions. JetBrains has a CUE plugin, but it's really barebones (doesn't even support jumping from the usage of a schema to its definition). Of course the possibilities when generating docs are endless (just think of the various syntaxes for doc comments, embedding examples/tests in source code etc.)...

It doesn't include validators for TOML and INI, but if you're doing JSON and YAML, I would take a look at using or building upon CUE (https://cuelang.org/). It is a different take on schema definition (plus more), and is surprising terse and powerful model.

Starlark in go https://github.com/google/starlark-go is a great way to combine the best of both, the ease of use of Python and the simplicity of go.

I have been building a platform for deploying internal web applications using this approach https://github.com/claceio/clace. Use Starlark to configure the application, the platform itself is built in go.

The big unknown is your task definition: what does user-defined logic look like? If you're expecting go code, that's gonna need some cleverness because of the compiled nature of it. There's a node runtime implemented in go if you want to provide sandboxed javascript (check the source of k6.io, it's the main one I know that uses it). If you want to provide building blocks and let them compose them, starlark might be a good choice.

Another one of those (with broader language support) is the Starlark language, which has a Go implementation: https://github.com/google/starlark-go

Every config format gets as complex to be touring complete in the end. We had similar problems and eventually got rid of that complexity and switched to starlark (the bazel config language), was a huge benefit for the tools. https://github.com/google/starlark-go "Starlark is a dialect of Python intended for use as a configuration language. Like Python, it is an untyped dynamic language with high-level data types, first-class functions with lexical scope, and garbage collection."

Direct link to the Go implementation of Starlark: https://github.com/google/starlark-go

For a Python-like syntax, https://github.com/google/starlark-go is the language used in Babel. It's very mature, but since it is used in a massive mature project with a specific purpose, it doesn't move fast or drift from the spec of its Java-based sibling. It doesn't have exception try except blocks or some other features you might expect, but for short extension logic, it might be exactly what you want with the stability you can depend upon.

Context: https://github.com/google/starlark-go/blob/cfacd890221418a2dc2c736f7b5e3476c38709b1/starlark/int_posix64.go

Thus envd is more like Dockerfile, while it uses a simplified python dialect starlark https://github.com/google/starlark-go as the build language.

Use Go (mostly for starlark-go)