I know Linux people love dependency hell and shared libraries all over their system, but keep that crap out of my Mac software. If it's not all in the app bundle, I don't want the software (this doesn't include app associated data, like sample libraries). The Mac App Store doesn't allow prerequisites. That then means developers will be fattening up their app packages or .net installers will come as part of every app package that needs it. Neither of which I want.
External linked/shared libraries and frameworks are legacy engineering concepts and marketing (to developers) that programmers just won't let die. Microsoft created an entire system folder wrapper/emulation subsystem just to try to deal with the decades of DLL hell that legacy DOS/Windows created with its sloppy system architecture and design guidelines (as in, no guidelines). We do not live in the days of tiny storage devices, so there's no need to avoid compiling your code into the binary. If you need to reuse code, so be it. Code reuse isn't the cause of bloat; bad code is.
If it's not provided by the OS API, it should be compiled into the binary, or at the very least never live outside the app bundle. Dependencies SUCK. Multiple objects to position in a user's file system sucks. That's why Microsoft has a pile of breakable shortcuts to executables inside cluttered application folder hierarchies, and Apple has a programs folder where you can pretty much put things wherever the hell you want to, as it should be.
