kcl VS community

KCL: A declarative configuration and policy programming language implemented by Rust, which improves the writing of a large number of complex configurations through mature programming language technology and practice, and is committed to building better modularity, scalability and stability around configuration, simpler logic writing, fast automation and good ecological extensionally.

Rust Ver. here

Have you considered using a different language for templating? this could be a BIG selling point. Some good ones are cue-lang (though I haven't seen support for rust), kcl or nickel-lang.

We usually use KCL as the DSL（ https://github.com/KusionStack/KCLVM ）Build a user interface abstraction (masking the Kuberetes concept that developers do not want to understand) and build different UIs based on this abstraction (it can be an IDE interface, a WebUI, or a CLI), which is very flexible and can quickly respond to the increasing demand for UI changes from developers. Alternatively, another approach is to quickly modify YAML through KCL's Mutation capability (different teams can use KCL to write different namespace conditions). And KCL can be combined with ArgoCD to achieve better results

Website: https://kcl-lang.io/

Sure, the IDE/Editor extension based on the kcl-language-server issue is here: https://github.com/KusionStack/KCLVM/issues/513

Welcome to our community: https://github.com/KusionStack/community

## https://github.com/KusionStack/KCLVM Kusion Configuration Language (KCL) is an open source constraint-based record and functional language. KCL improves the writing of a large number of complex configurations through mature programming language technology and practice, and is committed to building better modularity, scalability and stability around configuration, simpler logic writing, fast automation and good ecological extensionality. ## Features + **Easy-to-use**: Originated from high-level languages ​​such as Python and Golang, incorporating functional language features with low side effects. + **Well-designed**: Independent Spec-driven syntax, semantics, runtime and system modules design. + **Quick modeling**: [Schema](https://kusionstack.io/docs/reference/lang/lang/tour#schema)-centric configuration types and modular abstraction. + **Rich capabilities**: Configuration with type, logic and policy based on [Config](https://kusionstack.io/docs/reference/lang/lang/codelab/simple), [Schema](https://kusionstack.io/docs/reference/lang/lang/tour/#schema), [Lambda](https://kusionstack.io/docs/reference/lang/lang/tour/#function), [Rule](https://kusionstack.io/docs/reference/lang/lang/tour/#rule). + **Stability**: Configuration stability built on [static type system](https://kusionstack.io/docs/reference/lang/lang/tour/#type-system), [constraints](https://kusionstack.io/docs/reference/lang/lang/tour/#validation), and [rules](https://kusionstack.io/docs/reference/lang/lang/tour#rule). + **Scalability**: High scalability through [automatic merge mechanism](https://kusionstack.io/docs/reference/lang/lang/tour/#-operators-1) of isolated config blocks. + **Fast automation**: Gradient automation scheme of [CRUD APIs](https://kusionstack.io/docs/reference/lang/lang/tour/#kcl-cli-variable-override), [multilingual SDKs](https://kusionstack.io/docs/reference/lang/xlang-api/overview), [language plugin](https://github.com/KusionStack/kcl-plugin) + **High performance**: High compile time and runtime performance using Rust & C and [LLVM](https://llvm.org/), and support compilation to native code and [WASM](https://webassembly.org/). + **API affinity**: Native support API ecological specifications such as [OpenAPI](https://github.com/KusionStack/kcl-openapi), Kubernetes CRD, Kubernetes YAML spec. + **Development friendly**: Friendly development experiences with rich [language tools](https://kusionstack.io/docs/reference/cli/kcl/) (Format, Lint, Test, Vet, Doc, etc.) and [IDE plugins](https://github.com/KusionStack/vscode-kcl). + **Safety & maintainable**: Domain-oriented, no system-level functions such as native threads and IO, low noise and security risk, easy maintenance and governance. + **Production-ready**: Widely used in production practice of platform engineering and automation at Ant Group. ## What is it for? You can use KCL to + Generate low-level static configuration data like JSON, YAML, etc. + Reduce boilerplate in configuration data with the schema modeling. + Define schemas with rule constraints for configuration data and validate them automatically. + Organize, simplify, unify and manage large configurations without side effects. + Manage large configurations scalably with isolated configuration blocks. + Used as a platform engineering lang to deliver modern app with [Kusion Stack](https://kusionstack.io). ## How to choose? The simple answer: + YAML is recommended if you need to write structured static K-V, or use Kubernetes' native tools + HCL is recommended if you want to use programming language convenience to remove boilerplate with good human readability, or if you are already a Terraform user + CUE is recommended if you want to use type system to improve stability and maintain scalable configurations + KCL is recommended if you want types and modeling like a modern language, scalable configurations, in-house pure functions and rules, and production-ready performance and automation Welcome to out community: Search `KusionStack` on Slack