Slackware had always seemed both mysterious and masochistic to me.
You certainly learn a lot about paths, environment variables and compile options.
Slackware was my first and I didn't know that package managers existed (or maybe they didn't at the time) to resolve dependencies and even if they did, they probably lagged on versions. I learned true dependency hell when trying to build my own apache, sendmail, etc from source while missing a ton of dependency libraries (or I needed newer versions) and then keeping things relatively up to date. Masochistic? Definitely for me, but idk how much of that was self inflicted by not using the package tool. Amazing learning at the time. This would have been mainly Slackware 3.x and 4.x. I switched to Debian (not arch BTW).
What's the point of slakware, what exactly does it offer? When I was new arch user 15 years ago it was exactly the same, sparse updates, no package manager, limited support.
It's a unique combination of extreme stability and extreme KISS philosophy.
Sparse updates are a selling point for some people. You do get timely security updates, but you don't get "version number must go up".
For installing additional software there are 5 package managers that I know of, 4 of which resolve dependencies.
The base system doesn't need a fancy one because the installer already resolves all dependencies.
And as for support, there's well-written documentation installed with the system, and linuxquestions.org has a very active community where the main dev and the maintainers post regularly.
It's certainly not a good distro for most people, but it's the perfect one for roughly 10000 users worldwide.
Patrick Volkerding
Slackware users love the fact that precious Patrick builds the entire thing himself. They also really like the fact that it uses no modern Linux technologies, if it ain't broke don't fix it.
Slack be upon Him, and may his code ever compile without errors!
I mean, if you're an arch user you probably should get it, given it's kinda the same train if thought that brings most arch users to choose that.
The point is being a barebones system you can do what you want on top of, it tries to avoid making any choice for you.
I've kinda often thought of it as the step between LFS and Gentoo/Arch for users who want the most control over their system.
Where is the upper one from? I feel I could read something like that now
Looks familiar, like every second book from sci-fi golden age. You can read, Sargasso of Space.
Thanks for the recommendation
Cover of Utopia Zukunftsroman #299, 1961 by Karl Stephan. I'd never heard of it but it reminded me of the cover art for Truckfighters' album "Gravity X" (which itself is from the cover of an issue of Space:1999). Turns out he didn't do that cover but he did actually do some work for Space:1999.
Thanks!
Sure thing. I got on a fuzz rock and stoner metal kick for a while and that album cover stuck with me. Then the usual compulsion took over and I ended up on a deep dive through old sci-fi, pulp comics, etc.
Then what makes Debian its only a month younger than Slackware?

Maybe the only time the words Dick and Dyke appear together.
The annoying younger sibling?
After a run of RedHat - Fedora - OpenBSD - OSX to about 2007, I gave Debian more of a try in the form of #! Linux. That was a great minimalist distro. Ever since then it's just one Debian variant or another. It does the job with minimal fuss.
It really helps that I don't push the hardware with shiny new equipment or need much in 3D drivers. Linux Mint on desktops, Debian servers, Ubuntu only for driver issues, Raspian/Armbian on SBCs.
I'm partial to installing vanilla, headless Debian and then frankensteining everything together myself from there.
Nothing but the basics that way!
The hardest core version I saw someone do that was long ago. My best friend and I were using OpenBSD back in early 2000's. He installed a minimal install. From there he pulled the source tree makefiles. Then he started running make on Mozilla (pre firefox days). He just kept building, patching, fixing, and hammering away. Eventually he built the whole GUI environment, dependencies, and Mozilla which took that computer months to complete it all.
Today, he's the lead engineer for a massive tech company.
We are indeed still alive.
Here is what I don't understand about Slackware. Why does the installer recommend on installing everything. Not just a few applications most people might need. It recommends everything. Of course you can do a more minimalist installation but the installer recommends against it. Every application possible.
Because Slackware doesn't have dependency resolution in the base system.
Additional software you install from slackbuilds includes dependency info, but dependencies that are in the base system aren't mentioned.
The maintainers test against a full installation and anyone giving support assumes you have a full system.
You can do a more minimal install but then you're on your own. Similar to installing Arch without following the wiki.
Thank you for the great reply. I am not saying one way is better but coming from Debian that was very foreign to me. I have a lot of respect for Slackware and people who use it.
It is very foreign today and stems from a time without wide-spread internet access.
A distribution was a set of software on physical media. You bought it, you installed it, and your system stayed like that until the next release. So it made sense to include the kitchen sink. That way, the same distribution was useful to everyone, regardless of use case or personal preference.
Meanwhile NixOS users

alone and very far away from the real world?
yes but also superior beings who cannot connect to their erstwhile siblings anymore
Are they waiting for Slackware 5.0 to release finally?
good one!
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.