Mainly because Linux is built by developers for developers, this philosophy is pretty core to linux and effects every thing from a simple config file to package management. Couple this with some unfortunate industry trends, add in an aversion to the gui , and you get a preety prickly set of thorns to tackle when it comes to approaching linux.
The ‘for the dev by the dev’ will always be fundamental to linux, so i dont think linux will ever be a dream to configure setup and customize. there will always be a ‘new’ way to do what needs to be done and more than likely the best approach will be through the terminal, to modify what ever is needed.
and while this is intuitive to those who live an breathe the linux command terminologies and can type accurately 60 wpm or more, it may seem ‘easy peasy’.
but to those of us who are bit slower on the keyboard and can in no way type a single sentence with out using back space at least once … its pure hell.
As for the Industry Trends, the whole simpler is better and more secure by design trends we have been plagued with for the last several years has pretty much alienated many distros from a user base who wants to configure the OS, but dont want to have to jump through hoops for every custom tweak and/or process that may need elevated permissions.
Pretty much leaving us with 2 types of linux to work with . The its too simple and locked down variety thats fine for email and web, and the never ending, ‘edit this config file after this file and that file then this file and oh yeah be sure to have this package installed, oh its not there ?? well add this to that config file and try again’, Variety.
The whole System_d vs Init, im not entirely sure if this is whats responsible for some of the changes im seeing in linux but configuration has become even more burdensome, now requiring you to use a command to launch a process that launches a text editor that allows you to make changes to the config file .
(RANT)
WTH ?? why cant i just open up the damn config file and make the changes ??? but noooo it has to be done through the special command …
Again im not sure if system_d vs init is responsible for this, but it seems to have started popping up around that time. This added even more hoops to jump through to make changes to the OS. (/RANT)
Also not to mention the consumer industries aversion to linux open nature making simple things more difficult than necessary.
regardless the ever changing environment of linux its self, can be a bear.
i do see shimmers of light at the end of this tunnel as more and more distros have become a bit more approachable to those of us who need to configure the os a certain way, and gives you usable access to your hardware.
but sofar we still have a ways to go.