Editing Slackware (section)

==Design philosophy==
The design philosophy of Slackware is oriented toward [[unix philosophy|simplicity]], software purity,<ref>{{cite web|url=http://docs.slackware.com/slackware:philosophy|title=Slackware Philosophy|website=Docs.slackware.com|access-date=November 7, 2018|archive-date=November 5, 2018|archive-url=https://web.archive.org/web/20181105220539/http://docs.slackware.com/slackware:philosophy|url-status=live}}</ref> and a core design that emphasizes lack of change to upstream sources. Many design choices in Slackware can be seen as a heritage of the simplicity of traditional Unix systems and as examples of the [[KISS principle]].<ref>{{cite web|url=http://rlworkman.net/howtos/slackbasics.pdf|title=Slackware Linux Basics, Chapter 2|website=Rlworkman.net|access-date=July 22, 2017}}</ref> In this context, "simple" refers to the simplicity in system design, rather than system usage. Thus, ease of use may vary between users: those lacking knowledge of command line interfaces and classic Unix tools may experience a steep learning curve using Slackware, whereas users with a Unix background may benefit from a less abstract system environment.{{Citation needed|date=September 2014}} In keeping with Slackware's design philosophy, and its spirit of purity, most software in Slackware uses the original configuration mechanisms supplied by the software's authors; however, for some administrative tasks, distribution-specific configuration tools are delivered.