A Linux distro is a Linux distro, of course, so differences are subtle and particular. Any distro can be manipulated as much as anyone wants as long as they know how and they can deal with the implications of their changes.
Arch has more scaffolding -- dependency resolution, etc. -- which is all very nice but presents its own Arch-specific learning curve and tends to get in the way if you want to do something that the "Arch Way" does not encompass.
Slack users can build and install the very latest source from upstream if they wish, or they can choose not to.
Dependencies obviously exist in Slackware. They are how Linux is structured. But, for some strange reasons, perhaps, Slackware packages seem to have fewer of them.
A Linux distro is a Linux distro, of course, so differences are subtle and particular. Any distro can be manipulated as much as anyone wants as long as they know how and they can deal with the implications of their changes.
Arch has more scaffolding -- dependency resolution, etc. -- which is all very nice but presents its own Arch-specific learning curve and tends to get in the way if you want to do something that the "Arch Way" does not encompass.
Slack users can build and install the very latest source from upstream if they wish, or they can choose not to.
Dependencies obviously exist in Slackware. They are how Linux is structured. But, for some strange reasons, perhaps, Slackware packages seem to have fewer of them.