Publish/Save/Install-Module should handle binary dependencies using nuget pattern. Currently it is necessary to bundle binaries (bad!)
Currently the Module cmdlets apply standard nuget logic to referenced modules (download as needed, apply version restrictions, etc.), but not to binaries referenced by a module (and their dependencies).
This leads to module authors needing to package all referenced binaries (and dependency chains) in the module (e.g., on psgallery). This is an anti-pattern. This is why nuget exists. Aside from version control madness, this creates potential legal issues for module authors if they have a 3rd party binaries in their dependency chain. Now they could be "distributing" 3rd party code which is a very different matter from referencing 3rd party code.