For a well-organized ruby gems system, they're largely orthogonal (N + M resources).
Per-platform binaries expend resources proportional to the cross product (NM resources).
You also have to set up and maintain automated build systems for every platform and they form a whole additional set of dependencies for shipping every little point release.
For a well-organized ruby gems system, they're largely orthogonal (N + M resources).
Per-platform binaries expend resources proportional to the cross product (NM resources).
You also have to set up and maintain automated build systems for every platform and they form a whole additional set of dependencies for shipping every little point release.
Avoid it whenever possible.
edit: I always did think N should come before M