I wrote a blog post about the package / modules in miqula. https://medium.com/@bitteldany/a-case-for-binary-packages-7844fb1a4909

Interesting! Just a few days ago, I wrote a blog post saying that I'd like to have a module system in which each module's submodules are entirely independent of other (sub)modules in the system. If I understand your post correctly, miqula is such a system.

Yes. A miqula module is really more like a cache, which can be imported an directly used, but not edited, not "dived into*, can't even copy function contents out of it. I think it works great if it's closed like that, it gives a clear separation. Hopefully this also leads to better design. And you can always look into a module by closing miqula and opening the corresponding package file. If I read your blog correctly, you kind of want both of it. Closed (locked) and being able to inspect it.