Another major advantage of Miniwood is that if you activate compression, e.g. by setting
the Compress tag to True in the @OPTIONS preprocessor command or
by passing the -compress console argument, all libraries linked to
the executable compiled by Miniwood will be compressed as well, which will further
reduce the size of executables compiled by Miniwood.
This is a clear advantage over Hollywood because when activating compression with Hollywood, only the applet and plugins linked to the executable will actually be compressed. Hollywood's main runtime will remain uncompressed. This is different with Miniwood so if you care about small executables activating compression with Miniwood is the best way to get the smallest executables.
On arm64 macOS you should always enable compression when using Miniwood because arm64 macOS enforces a Mach-O segment alignment of 16kb which means there is a lot of empty padding space in Miniwood's libraries so they aren't as compact as on the other platforms which use smaller segment alignments. So if you care about small filesizes on arm64 macOS, you should definitely activate compression to work around the 16kb segment alignment issue.