Hi Andrew, thanks for your comment! Maybe I should clarify this feature a little bit more in my next articles, but these remote imports aren't at all the same as the ones Deno does.

Deno remote imports fetch a file and import it into the runtime, I agree with you that they make version control harder, and cause lots of other issues. We do not have, and will never have that feature in Clio.

The remote imports in Clio, are to import micro-services or functions from API endpoints (or a FaaS). You can use this feature to host your functions on your remote server, then call them in the browser or elsewhere remotely, or you can use this feature to benefit from the resources available to you over the network somewhere else.

Want to run a function on 1000 cpu cores? No problem, host them each on a separate machine and import it from one single entry point: caching, serialization, load balancing, message queue and everything else is already taken care of.

Want to import and use a Python library? No problem, wrap the Python function using the Clio RPC library for Python (WIP), host it and import it over the network!