Which are great things for prototyping but, for distributing things, virtual environments (or unversioned/tagged dependencies) and 3rd party package managers are a finnicky and brittle hurdles that make the end user's lives worse. What's more is that, without a legitimate type system, long term maintenance becomes a recurring pita. Exceptions are also problematic in that they blow up stacks of dependent computation rarely shrink over time without extensive rewriting. It's also still a relatively slow language, which should be disqualifying for a performance sensitive project like this.

Doesn't even need to be as tough as rust; There're languages that're as easy to write. Go, for one, supports iterative workflows (there're some community repls which, sadly, are usually versions behind but the compiler is very fast) and garbage collection and makes distribution/acquisition trivial. There're versions of it that are more script-oriented and even have generator expressions and other declarative syntax features.

After you asked, I elaborated in a response to @solumbran but feel free to ask in more detail or disagree

Hate to break it to you but AWS CLI is not the gold standard in software development and distribution

So are yours. They're just shared by companies evrybody hates.