Breaking - cleanup + remote packages in

docs/README.md

@@ -33,9 +33,6 @@ We also explicitly use that "_piece of software_" as the interpreter name it ref
 
  * [pyodide](https://pyodide.org/en/stable/index.html) is the name of the interpreter that runs likely the most complete version of latest *Python*, enabling dozen official modules at run time, also offering a great *JS* integration in its core
  * [micropython](https://micropython.org/) is the name of the interpreter that runs a small subset of the *Python* standard library and is optimized to run in constrained environments such as *Mobile* phones, or even *Desktop*, thanks to its tiny size and an extremely fast bootstrap
- * [ruby-wasm-wasi](https://github.com/ruby/ruby.wasm) is the name of the (currently *experimental*) interpreter that adds *Ruby* to the list of programming languages currently supported
- * [wasmoon](https://github.com/ceifa/wasmoon) is the name of the interpreter that runs *Lua* on the browser and that, among the previous two interpreters, is fully compatible with all core features
- * [webr](https://docs.r-wasm.org/webr/latest/) is the name of the (currently *experimental*) interpreter that adds *R* to the list of programming languages currently supported
 
 `<script>` tags specify which *interpreter* to use via the `type` attribute. This is typically the full name of the interpreter:
 
@@ -49,18 +46,6 @@ We also explicitly use that "_piece of software_" as the interpreter name it ref
     import sys
     print(sys.version)
 </script>
-
-<script type="ruby-wasm-wasi">
-    print "ruby #{ RUBY_VERSION }"
-</script>
-
-<script type="wasmoon">
-    print(_VERSION)
-</script>
-
-<script type="webr">
-    print(R.version.string)
-</script>
 ```
 
 ℹ️ - Please note we decided on purpose to not use the generic programming language name instead of its interpreter project name to avoid being too exclusive for alternative projects that would like to target that very same Programming Language (i.e. note *pyodide* & *micropython* not using *python* indeed as interpreter name).
@@ -818,14 +803,11 @@ Please note that if a worker is created explicitly, there won't be any element,
 | :------------- | :---: | :--------: | :--------: | :----------------: | :---------: | :---------: |
 | pyodide        | •     | •          | •          | •                  | •           | •           |
 | micropython    | •     | •          | •          | •                  | •           | •           |
-| ruby-wasm-wasi | •     | •          | •          | !                  |             |             |
-| wasmoon        | •     | •          | •          | !                  | •           |             |
-| webr           | r     | •          | re         |                    |             |             |
 
   * **run** allows code to run synchronously and optionally return value
   * **runAsync** allows code to run asynchronously and optionally return value
   * **runEvent** allows events to be invoked and receive the `event` object
-  * **registerJSModule** allows `from polyscript import Xworker` or registration of arbitrary modules for *custom types*. It currently fallback to globally defined reference (the module name) whenever it's not possible to register a module (i.e. `polyscriptXWorker` in Lua or `$polyscript.XWorker` in Ruby).
+  * **registerJSModule** allows `from polyscript import Xworker` or registration of arbitrary modules for *custom types*. It currently fallback to globally defined reference (the module name) whenever it's not possible to register a module.
   * **writeFile** it's used to save *fetch* config files into virtual FS (usually the one provided by Emscripten). It is then possible to import those files as module within the evaluated code.
   * **transform** allows `xworker.sync` related invokes to pass as argument internal objects without issues, simplifying as example the dance needed with *pyodide* and the `ffi.PyProxy` interface, automatically using `.toJs()` for better DX.