comma VS cue

Nowadays, I tend to try things out with comma, then add them to my configuration for later use. Some tools are not even installed in my systems because I use them so infrequently - opening a terminal and running , freecad is basically as easy as actually having it installed.

There's a version of this approach that uses nix-index to figure out which package a command is in called comma: https://github.com/nix-community/comma

Relatedly, check out comma. It's basically a shortcut prefix command that will search packages for the binary you want to run (via nix-index), and gives you an interactive choice if there are multiple. Which package was drill in again? No matter, I'll just prefix a comma :)

https://github.com/nix-community/comma

this + if you want to run a command automatically I suggest comma

Yeah dude. Emphemeral installs are a feature, not a bug. Similar vein is , https://github.com/nix-community/comma

You're looking for https://github.com/nix-community/comma

One of the nicest tools is comma. https://github.com/Shopify/comma. It's just a light weight wrapper around searching nix-pkgs and running something, but it sure makes a lot of things easier when you're sharing somebody else's laptop.

If you want to test out some program, I would STRONGLY recommend using nix-shell -p . This will create temporary environment, that will allow you to test out the package. You can also check out comma.

I love using Shopifys comma tool https://github.com/Shopify/comma cause it's so useful for just small programs that u need to run once and then forget about them

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.