f this before choosing FFI bindings over a traditional
native module. It is also possible to use a hybrid approach, where some core functionality is exposed via a
C extension module, and the majority of an API is bound via FFI.
</p>
<p>The FFI Module contains both the low-level primitives to load dynamic libraries (as with <code class="mendoza-code">dlopen</code> on posix systems), get
function pointers from those modules, and call those function pointers. On top of this, there is a macro based abstraction 