Thanks to all 3 :) ... Ryelang in sort of "not a concern at this stage" and "go with the flow" way currently has this idea of per project static binary with all dependencies compiled in.

It sounds a little odd at first, but besides being the simplest to implement in Go, this also solves a problem for which Python needs tools like venv, pyvenv, virtualenv, ... that also this blog post mentions. The sheer number of these tools shows that this is a problem and that maybe that the solutions aren't optimal.

It also offloads most of package management (ie. pip like stuff) to just "go mod".

A specific binary per project also has other benefits in terms of securing the running environment, I think ... I'm still exploring this.

This is not yet in focus, but maybe starting from a totally different position will make some interesting or simpler tooling possible.