sublime-json5
skycfg
sublime-json5 | skycfg | |
---|---|---|
1 | 6 | |
3 | 634 | |
- | 0.5% | |
2.7 | 3.9 | |
5 months ago | about 2 months ago | |
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.
sublime-json5
-
YAML: It's Time to Move On
I like it so much I got motivated enough to start making a sublime text highlighter for it. I got a bit lost though, having never made one before.
And then I tried to use a tool called SBNF to write the grammar for the language at a high level and have it spit out Sublime Text syntax highlighting code. Didn't quite work yet unfortunately.
https://github.com/bschwind/sublime-json5
https://github.com/BenjaminSchaaf/sbnf
skycfg
-
Jsonnet – The Data Templating Language
I can definitely sympathize here - in every context, just straight JSON/YAML configuration seems never expressive enough, but the tooling created in response always seems to come with sharp edges.
Here are some of the things I appreciate about Jsonnet:
- It evals to JSON, so even though the semantics of the language are confusing, it is reasonably easy to eval and iterate on some Jsonnet until it emits what one is expecting - and after that, it's easy to create some validation tests so that regressions don't occur.
- It takes advantage of the fact that JSON is a lowest-common-denominator for many data serialization formats. YAML is technically a superset of JSON, so valid JSON is also valid YAML. Proto3 messages have a canonical JSON representation, so JSON can also adhere to protobuf schemas. This covers most "serialized data structure" use-cases I typically encounter (TOML and HCL are outliers, but many tools that accept those also accept equivalent JSON). This means that with a little bit of build-tool duct-taping, Jsonnet can be used to generate configurations for a wide variety of tooling.
- Jsonnet is itself a superset of JSON - so those more willing to write verbose JSON than learn Jsonnet can still write JSON that someone else can import/use elsewhere. Using Jsonnet does not preclude falling back to JSON.
- The tooling works well - installing the Jsonnet VSCode plugin brings in a code formatter that does an excellent job, and rules_jsonnet[0] provides good bazel integration, if that's your thing.
I'm excited about Jsonnet because now as long as other tool authors decide to consume JSON, I can more easily abstract away their verbosity without writing a purpose-built tool (looking at you, Kubernetes) without resorting to text templating (ahem Helm). Jsonnet might just be my "one JSON-generation language to rule them all"!
---
Though if Starlark is your thing, do checkout out skycfg[1]
[0] - https://github.com/bazelbuild/rules_jsonnet
[1] - https://github.com/stripe/skycfg
-
The Dhall Configuration Language
Can you say more about what GCL does better than all of the open source ones?
Anecdotally, I've heard a lot of GCL horror stories, and many Xooglers have chosen to create things like Jsonnet or Skycfg (https://github.com/stripe/skycfg) instead.
- YAML: It's Time to Move On
- Opinion-driven design
-
Migrating Millions of Concurrent WebSockets to Envoy
If you’re looking at other solutions check out https://github.com/stripe/skycfg It works with Envoy and lots of other things that support protobuf configs
-
Yaml Is The Worst Thing Ever Created K8s Should
This is good and there are several other options like https://github.com/stripe/skycfg#why-use-skycfg to add full language support (using Go or python for ex) to configurations.
What are some alternatives?
nestedtext - Human readable and writable data interchange format
jsonnet - Jsonnet - The data templating language
prettier - Prettier is an opinionated code formatter.
isopod - An expressive DSL and framework for Kubernetes configuration without YAML
babashka - Native, fast starting Clojure interpreter for scripting
yq - Command-line YAML, XML, TOML processor - jq wrapper for YAML/XML/TOML documents
ron - Rusty Object Notation
openapi-python-client - Generate modern Python clients from OpenAPI
rules_jsonnet - Jsonnet rules for Bazel
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
starlark - Starlark Language