github-desktop
isopod
github-desktop | isopod | |
---|---|---|
1 | 4 | |
1 | 462 | |
- | 0.4% | |
0.0 | 0.0 | |
6 months ago | 6 months ago | |
TypeScript | Go | |
MIT License | Apache License 2.0 |
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.
github-desktop
-
Jsonnet – The Data Templating Language
Yes that's a common problem with config languages. They're torn between competing priorities:
1. Fast to parse with a small engine, good error messages, safe to evaluate.
2. Powerful, can express config with arbitrary logic.
In Conveyor we try an alternative approach. The config is HOCON, which is a superset of JSON syntax designed for human readability/writability/convenience first and foremost, so it's got a very nice and clean feel to it. You can see an example here:
https://github.com/hydraulic-software/github-desktop/blob/co...
It can be parsed with a normal-sized config library and the errors you get are reasonable.
But then what if you hit the limits of what it can express? We added support for "hashbang includes":
include "#!script.js"
isopod
-
Jsonnet – The Data Templating Language
Tried it[0], worked reasonably well. Be prepared for strong opposition from traditional “devops” folks “who don’t mind yaml” and will drag everyone down.
[0] - https://github.com/cruise-automation/isopod
- Deploying Kubernetes clusters in increasingly absurd languages
- YAML: It's Time to Move On
-
Cue: A new language for data validation
I like Cue and Jsonnet and Starlark and so on. But all of these have very low mindshare (though Starlark has the most momentum thanks to Bazel), and who knows if they will be dead by next year.
Being an early adopter is difficult both in terms of the immaturity of the tooling — Cue, for example, only has a Go implementation at the moment — and in terms of the risk of betting on an evolutionary dead end, which can cause a lot of unnecessary churn when you want to standardize on something across an entire organization.
As a concrete example, I'd love to replace Kubernetes's use of YAML with something like the above. But the tooling is immature, and almost nobody is using any of it. For example, there's Isopod [1], which is a nice-looking tool to use Starlark with Kubernetes. But it might go the same way as Ksonnet.
[1] https://github.com/cruise-automation/isopod
What are some alternatives?
kubectl-neat-diff - De-clutter your kubectl diff output using kubectl-neat
skycfg - Skycfg is an extension library for the Starlark language that adds support for constructing Protocol Buffer messages.
rules_jsonnet - Jsonnet rules for Bazel
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
kubecfg - A tool for managing complex enterprise Kubernetes environments as code.
sprig - Useful template functions for Go templates.
hof - Framework that joins data models, schemas, code generation, and a task engine. Language and technology agnostic.
c2bf - Compiler from C to brainfuck
ursonnet - experimental ur-cause tracer for jsonnet
jk - Configuration as Code with ECMAScript