Camilo

If we need some blueprints for what can be inside the CLI as Standard libs, we can look into other projects for their standard libs. Here is the standard libs...

Python has a wonderful extensive library. But they got 30+ years of development and millions of dollars of funding by corporate overlords xd. So my proposal is start small with...

Yes thats a good long term objective. But I doubt we want a `wren_cli` with too much weight on its binary. So most of those future libs can be delivered...

One idea is to limit the size of the binary of `wren_cli`. That way it cannot grow more than that to be manageable. A good maximum sice I think would...

That limit was based when I mix static libs from other langs to Wren CLI - Golang standard static lib weights around 2 MB - Haskell standard static lib weights...

I think Wren CLI should follow the unix [UNIX philosophy of do one thing and do it well](https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_and_Do_It_Well) So we can separate those ideas in different projects - A Wren...

So. Which modules should be inside `wren_cli`?. Modules that would not require a dynamic libraries to function. And will be statically linked to the binary, so it will add some...

While I agree having a "batteries included" binary would be nice to have. Wren CLI have a bus factor of 1. This means that we depend on Ruby's availability to...

Ok will do some testing :) is this the PR right? https://github.com/wren-lang/wren-cli/pull/71

Sorry my bad, I was just closing many issues to keep my pending list tidy. Linking to the issue https://github.com/wren-lang/wren-cli/pull/71