Originally Posted by repo
You can configure and do most things using the GUI, just like the other distro's.
Saying you need to know and use the CLI in order to use and configure slackware isn't correct.
There are enough GUI apps to do so, just like in the other distro's.
I interpreted 'the things behind' from the OP as working with the CLI and understand what happens.
This you can do with every distro, not only slackware.
I asked for extension & clarification to see where you are coming from & talking about.
Sorry, but you are just spinning here.
You can configure with the visual shell of choice by selection of a Environment that will allow you make the changes as long as you are root for configure action. If your going to utilize & depend on KDE then it's going to be hit & miss with UI & API. Good Luck! If you are going to use a console within the environment then that to is just a shell to provide cli.
One point that every Gnu/Linux(include Slackware) are still having issues with is wireless devices. Sure some Gnu/Linux have a turn key solution that sometimes works. But what are you going to do when it doesn't? Another GUI into another...?
You're going to be better off configuring Slackware from the console 'cli' since you will have the absolute control and not rely on a author who hopefully does things correct.
Preference for configuration should be from the cli to prevent any unknowns from alternate or different means of configuration. Sure, we as Slackware users do depend and rely on PV & team for proper system generation but after that one should rely on their own understanding and experience to configure & repair a Slackware system.
Not someone's custom script configured to streamline a Slackware system unless that person is a trusted contributor.
But again, it's your Slackware system to configure, use & maintain the way you desire and capable to do. From my point, it's safer therefore less chance of problem(s) if one learns to configure from the command line.