In my journey to try out other init systems after such extensive usage of systemd I wanted to also some alternative distributions as well. While I used Slackware in the past I only explored it from a very surface level, never diving too deep into the complexities that make it unique to to other distros. I have written comments about it in the past, and have never directly recommend it. I usually lump Slackware proper in with Gentoo and Debian as slow release user focused stability distros.
As you can tell, Slackware's release cycle as similar to Debian's. With a 'Release when ready' mentality. Volkerding for over almost 33 years has kept several core principals in every iteration and release of Slackware.
The KISS 'keep it simple, stupid' ideal, Slackware has no hidden magic or specialty. Packages are delivered as plain tarballs (*.tgz) with simple installpkg / removepkg scripts. There is no dependency resolver that silently pulls in dozens of libraries you never asked for they are handled by the user. Configuration files are text, most system settings live in /etc as human readable files (/etc/rc.d/rc.sysinit, /etc/inittab, /etc/hosts) and editing them directly is encouraged.
Slackware directly follows the Unix philosophy of one tool, one job. Volkerding makes Slackware stick to the classic Unix toolbox: sed, awk, grep, bash, make. When you need to accomplish a task, you learn the underlying command rather than clicking a GUI button or using a different stack of tools available in other distributions for ease of use on the user. Everything is explicit, the init scripts in /etc/rc.d/ are simple shell scripts that you can read line by line. And forces users to learn utils or manually download alternatives and fix dependency issues.
This focus on control over convenience is a pillar of Slackware and in my mind can only be compared to Gentoo in experience. You are the installer, while a text based installer LILO is available in Slackware, with the LILO installer, it does little to assist you in selection, expecting users to use the LILO --help options to read and follow through the installation, similar to current Arch installers but without the graphical flourishes. It asks you which partitions to format, which packages to install, and how to configure the network. No 'auto‑partition' wizard that decides for you. Package management is also manual, slackpkg automates updates, but you can also bypass it and install any .tgz you download. This teaches the user how the package system works under the hood and does more (I feel) for educating a user on package management than other distributions.
While the widespread adoption of systemd is commonplace in the current day, Slackware has kept and continued to keep the user selection available in mainline Slackware without needing a fork like Artix or Devuan. And what eventually led me to test these different init systems in Slackware over another distribution.
While not requiring a user to know init systems and having a default available, Slackware allows a user or at least encourages them to read about init systems, and their differences. You learn how the early boot process works with kernel, init, runlevels, and services. Something that many modern distros abstract away from in attempt to keep installation and selection simple. Making Slackware unique by allowing full user freedom of choice.
I find Slackware's package manager to be more fun and interesting than Debian's apt. I have used apt and aptitude for so long I felt like a fish out of water without dependency resolution, package stacks, and transitional package tagging. But the experience was refreshing and had me reading more about the packages I install more than usual, but I am not upset about it. I had to keep a notepad with the basic commands on it so I would remember basic resolution and what everything did. While I was not taken aback by most of the commands as most package managers function the same, if I was a new Linux user I can see this as being quite the learning experience.
Slackpkg like other package managers automates repository sync, package upgrades, and cleaning. However I find it bridges manual management with a simple update workflow. You become comfortable with the idea that a package is just an archive, plus a few shell scripts. No opaque metadata, no hidden dependency pulls.
The Slackware community I feel has a more cohesive learning ecosystem. The documentation is great and concise, not as well documented as the ArchWiki but very clear cut on issues and resolutions. And after some deep lurking on #Slackware IRC Channels (#slackware on Libera.Chat) I find that many of my questions and comments about the distro to be both common place and easily answered by members of the community. Because Slackware does not hold your hand and requires some documentation reading, the community is full of people who do the hand holding by sharing knowledge, not by hiding complexity, and empathizing with your questions with shared experience and commonality. It made me feel welcome to use the system given and often met with a "Best of luck" after with the hopes you too become part of a tradition of self reliance and peer teaching.
While using Slackware I was taking notes along the way, using my normal Debian installation workflow and experimentation 'how fast can I break it' mentality. And I was recording each action as I was working. And I wanted to compare it to other distributions or at least my experience compared to other distros.
Slackware excels when you want to understand how the system works, similar to Arch. Debian / Fedora / OpenSUSE excel when you want to be productive quickly. Both approaches are valuable, the key is to experience both sides. A developer who can comfortably switch between a 'black box' distro and a 'glass‑box' distro becomes a more versatile problem solver. While I am extremely comfortable with Debian and will most likely switch back to it in the future. Slackware will be my ultimate fallback if Debian ever makes me jump ship. I have learned quite a bit from using Slackware and feel like I can enjoy the system more. For others wanting to use Slackware I have some recommendations.
The educational value of Slackware cannot be understated, I enjoyed my time using it and it forced me to do something I have not done in a long time, read a man-page. I appreciate Slackware's minimalism from a security standpoint, reduces attack surface, and it's community is quick to address issues. The small footprint and lack of heavy background services make Slackware attractive for tinkerers and enthusiasts. I can enjoy the preservation of the Linux heritage, as many distros adopt systemd and other one size fits all solutions, Slackware remains a living reference for the original Unix like design. It creates a counter balance to the dominating introduction software and user friendly adoption of 'click to install' designs Slackware reminds me that understanding beats convenience for long term competence.