The reasons given on the readme seem to be more technical than functional/practical: > A proper audio plugin should be self-contained as much as possible, as t

The reasons given on the readme seem to be more technical than functional/practical: > A proper audio plugin should be self-contained as much as possible, as to not interfere with the DAW/Host. (...) A self-contained plugin can't be overstated, as DLL/shared-object symbol conflicts can trigger hard-to-debug crashes. I'm fine with the limitations, and like the idea of a self-contained plugin that does not phone home. And in my experience, Cardinal is already very solid and feature-complete, even in its beta form. But one could absolutely imagine a system where you can share setups that use modules that may or may not be available. For instance, you can build, save and share combinators in Reason that use non-standard REs.