featbit VS kcl

Feature flags, also known as feature toggles, have become an essential tool for modern software development. They enable developers to control the release of new features and updates in a flexible and controlled manner. In this blog post, we'll explore what feature flags are, their classical and modern use cases, and how to implement them effectively in front-end, mobile, and server-side applications. We'll also delve into the concept of overlapping design A/B testing and how feature flags play a crucial role in building robust experimentation.

Here's our issue link: [Good First Issues]: Configuring Serilog through appsettings.json file · Issue #520 · featbit/featbit (github.com)

featbit/featbit: A scalable, fast and 100% open-source feature flag tool written in C# .NET (github.com)

You can find the tool at: https://github.com/featbit/featbit

Hi everyone, I wanted to introduce a new open-source feature flag management tool that we recently discovered and implemented in our production environment. You can find the tool at: https://github.com/featbit/featbit We tested several other tools, but what convinced us to choose this particular tool were the following reasons: 1. It offers all the necessary functionalities we require. Additionally, it seems that they continue to open-source additional functions that other tools don't provide, such as Audit Logs, Reusable Segments, Permission Control, and even Single Sign-On (SSO) in the future. 2. I joined their community, and I found the core team to be friendly and responsive (perhaps because they are relatively new). 3. The tool is developed using a programming language that aligns well with our daily work. 4. Although they open-sourced the project only 7 months ago, they have been working on its development for two years. 5. It is licensed under the MIT license. I thought it would be helpful to share this tool here for anyone who may need it or wants to add it to your wishing list. Enjoy!

It's MIT for those interested in such things

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