From d858ada5fdbacb5a752b8d1285eace1dfc80cb7f Mon Sep 17 00:00:00 2001 From: peefy Date: Thu, 2 Nov 2023 13:27:02 +0800 Subject: [PATCH] docs: add more explanations in the comparison section with cdk8s Signed-off-by: peefy --- docs/user_docs/getting-started/intro.md | 2 +- .../current/user_docs/getting-started/intro.md | 2 +- .../version-0.7.0/user_docs/getting-started/intro.md | 2 +- versioned_docs/version-0.7.0/user_docs/getting-started/intro.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/user_docs/getting-started/intro.md b/docs/user_docs/getting-started/intro.md index bae0563a..b377a609 100644 --- a/docs/user_docs/getting-started/intro.md +++ b/docs/user_docs/getting-started/intro.md @@ -193,7 +193,7 @@ CDK's high-level language integrates well into application projects, effectively General-purpose languages can often be over-engineered, going beyond the requirements of the problem being solved. These languages can also present various security issues, such as problems with the ability boundary, such as accessing I/O, network, code infinite looping, and other security risks. In specialized fields, such as music, there are special notes used to communicate effectively, which cannot be expressed clearly in general-purpose languages. -Furthermore, general-purpose languages come in a variety of styles, which can create challenges in terms of unified maintenance, management, and automation. These languages are generally better suited to writing the client runtime, which is a continuation of the server runtime. They are not ideal for writing configurations that are independent of the runtime, as they are compiled into binaries and started from the process, making stability and scalability challenging to control. In contrast, configuration languages are often used to write data combined with simple logic, and they describe the expected final result, which is then consumed by the compiler or engine. +Furthermore, general-purpose languages come in a variety of styles, which can create challenges in terms of unified maintenance, management, and automation. These languages are generally better suited to writing the client runtime, which is a continuation of the server runtime. They are not ideal for writing configurations that are independent of the runtime, as they are compiled into binaries and started from the process, making stability and scalability challenging to control. In contrast, configuration languages are often used to write data combined with simple logic, and they describe the expected final result, which is then consumed by the compiler or engine. Besides, KCL is declarative and structured, and we can use KCL's automation API to modify and query the KCL code itself. ### vs. OPA/Rego diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/getting-started/intro.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/getting-started/intro.md index 8d2e65fd..4a81086f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/getting-started/intro.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_docs/getting-started/intro.md @@ -193,7 +193,7 @@ KCL 自然提供了 Helm 功能的超集以及 Helm KCL 插件，因此您可以 通用语言通常远远超出了需要解决的问题，例如安全问腿、能力边界问题（启动本地线程、访问 IO、网络、代码无限循环和其他安全风险）。例如，在音乐领域，有专门的音符来表达音乐，这便于学习和交流，它不能用一般语言表达清楚。 -此外，由于通用语言风格多样，需要统一维护、管理和自动化。通用语言通常用于编写客户端运行时，它是服务器运行时的延续，不适合编写独立于运行时的配置，被编译成二进制文件，并最终从进程开始运行。此外，GPL 稳定性和可扩展性不易控制。然而，KCL 配置语言通常用于编写数据，将数据与简单逻辑相结合，它描述了预期的最终结果，然后由编译器或引擎使用，既具备丰富的编程抽象能力，又具备方便的数据处理方式。 +此外，由于通用语言风格多样，需要统一维护、管理和自动化。通用语言通常用于编写客户端运行时，它是服务器运行时的延续，不适合编写独立于运行时的配置，被编译成二进制文件，并最终从进程开始运行。此外，GPL 稳定性和可扩展性不易控制。然而，KCL 配置语言通常用于编写数据，将数据与简单逻辑相结合，它描述了预期的最终结果，然后由编译器或引擎使用，既具备丰富的编程抽象能力，又具备方便的数据处理方式。此外，KCL 是声明式且结构化的，我们可以使用 KCL 的自动化 API 来对 KCL 代码本身进行修改和查询。 ### vs. OPA/Rego diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/getting-started/intro.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/getting-started/intro.md index 8d2e65fd..4a81086f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/getting-started/intro.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.7.0/user_docs/getting-started/intro.md @@ -193,7 +193,7 @@ KCL 自然提供了 Helm 功能的超集以及 Helm KCL 插件，因此您可以 通用语言通常远远超出了需要解决的问题，例如安全问腿、能力边界问题（启动本地线程、访问 IO、网络、代码无限循环和其他安全风险）。例如，在音乐领域，有专门的音符来表达音乐，这便于学习和交流，它不能用一般语言表达清楚。 -此外，由于通用语言风格多样，需要统一维护、管理和自动化。通用语言通常用于编写客户端运行时，它是服务器运行时的延续，不适合编写独立于运行时的配置，被编译成二进制文件，并最终从进程开始运行。此外，GPL 稳定性和可扩展性不易控制。然而，KCL 配置语言通常用于编写数据，将数据与简单逻辑相结合，它描述了预期的最终结果，然后由编译器或引擎使用，既具备丰富的编程抽象能力，又具备方便的数据处理方式。 +此外，由于通用语言风格多样，需要统一维护、管理和自动化。通用语言通常用于编写客户端运行时，它是服务器运行时的延续，不适合编写独立于运行时的配置，被编译成二进制文件，并最终从进程开始运行。此外，GPL 稳定性和可扩展性不易控制。然而，KCL 配置语言通常用于编写数据，将数据与简单逻辑相结合，它描述了预期的最终结果，然后由编译器或引擎使用，既具备丰富的编程抽象能力，又具备方便的数据处理方式。此外，KCL 是声明式且结构化的，我们可以使用 KCL 的自动化 API 来对 KCL 代码本身进行修改和查询。 ### vs. OPA/Rego diff --git a/versioned_docs/version-0.7.0/user_docs/getting-started/intro.md b/versioned_docs/version-0.7.0/user_docs/getting-started/intro.md index bae0563a..b377a609 100644 --- a/versioned_docs/version-0.7.0/user_docs/getting-started/intro.md +++ b/versioned_docs/version-0.7.0/user_docs/getting-started/intro.md @@ -193,7 +193,7 @@ CDK's high-level language integrates well into application projects, effectively General-purpose languages can often be over-engineered, going beyond the requirements of the problem being solved. These languages can also present various security issues, such as problems with the ability boundary, such as accessing I/O, network, code infinite looping, and other security risks. In specialized fields, such as music, there are special notes used to communicate effectively, which cannot be expressed clearly in general-purpose languages. -Furthermore, general-purpose languages come in a variety of styles, which can create challenges in terms of unified maintenance, management, and automation. These languages are generally better suited to writing the client runtime, which is a continuation of the server runtime. They are not ideal for writing configurations that are independent of the runtime, as they are compiled into binaries and started from the process, making stability and scalability challenging to control. In contrast, configuration languages are often used to write data combined with simple logic, and they describe the expected final result, which is then consumed by the compiler or engine. +Furthermore, general-purpose languages come in a variety of styles, which can create challenges in terms of unified maintenance, management, and automation. These languages are generally better suited to writing the client runtime, which is a continuation of the server runtime. They are not ideal for writing configurations that are independent of the runtime, as they are compiled into binaries and started from the process, making stability and scalability challenging to control. In contrast, configuration languages are often used to write data combined with simple logic, and they describe the expected final result, which is then consumed by the compiler or engine. Besides, KCL is declarative and structured, and we can use KCL's automation API to modify and query the KCL code itself. ### vs. OPA/Rego