From fbabac8c86d5db12100edf5844a5eba345ec9ed4 Mon Sep 17 00:00:00 2001 From: Jack Zhao Date: Sun, 24 Sep 2023 18:27:15 -0700 Subject: [PATCH] Update comparison.md --- docs/src/content/docs/guides/comparison.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/content/docs/guides/comparison.md b/docs/src/content/docs/guides/comparison.md index 5fa9e0c..2b53ba3 100644 --- a/docs/src/content/docs/guides/comparison.md +++ b/docs/src/content/docs/guides/comparison.md @@ -11,4 +11,4 @@ Pyodide does not setup web workers out of the box. If you site is [crossOriginIs ## PyScript -[PyScript](https://pyscript.net/) is great for configuring a single html page to run python code as well as providing acess to DOM through its `pyweb` API. `PyScript` adopts an RPC pattern while `PySandbox` is closer to be a REST-like API. If you are using a JS web-framework (e.g. a React-based framework) to build your web application, you may find `PySandbox` easier to use because of its pure JS-based invocation. +[PyScript](https://pyscript.net/) is great for configuring a single html page to run python code as well as providing acess to DOM through its `pyweb` API. `PyScript` adopts a RPC pattern by letting Python code manipulate the DOM and react to events, while `PySandbox` is intended to be a traditional REST backend. If you are using a JS web-framework (e.g. a React-based framework) to build your web application, you may find `PySandbox` easier to use with its pure JS invocation without needing to rely on `