rayql VS kcl

That's why I created RayQL, a schema definition and query language for SQLite, built with Rust. The core goal is to provide a compact and familiar syntax that eliminates the need to reinvent the wheel for data validation, allowing you to quickly prototype and build backends without juggling multiple components. With RayQL, everything you need lives in a single executable, which makes it super-easy to get started on your side projects.

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