I feel much the same.rambo919 wrote: ↑Fri Dec 04, 2020 2:46 amThe difference is there are many GUI third party windows apps that randomly pop up to fill the gaps. Lots of automation happens which means you do not need to read any documentation after a while and can operate on autopilot.t42 wrote: ↑Thu Dec 03, 2020 12:41 pmSome people in this and other topics frequently complain about the lack of the documentation and step by step guides. I understand it can be frustrating when you donated hundreds of your dollars or euros to some Linux team and still can't get off the ground in the documentation department. Anyway there is better option - any IBM UNIX operating system possesses volumes of this staff (small example Setting up a cluster for an air gap environment ) with price range starting from 1000 USD/month. On the other side I don't remember any comprehensive useful Windows documentation supplied; it comes to mind only some basic manuals available with Compaq systems before years 2000.
For linux though it gets problematic because there is so many things you can put in so many text files and so many services that you have to restart manually...... how can most people not get lost in the weeds? Even the step by step guides get randomly outdated and you can end up bricking a system following old guides especially in my own experience dealing with Samba, grub or systemd. I still cannot figure out how to best manually tune nvidia graphics settings with all the changes in the last few years.
Systemd might be a great thing for many people but it has WAY too many seperate config files that seem to point to one another in obscure ways.
And then there is the experience I had trying to compile gnucash manually using the recommended path..... which creates a messy opt folder /home. I immediately deleted this abomination and was forced to install the flatpak which also is messy and WAY too big but at least the system seems capable of sorting itself better.
The OCD in me simply cannot stand the messy way linux compulsively sprawls programs across the entirety of the system.
In stark contrast to that is the way RISC OS used to organise it's applications - In the application's own folder! - No problem with dependencies or missing libraries - It's what AppImage is now, basically. You copy the folder, you copy the application, nothing to install, just copy and double-click. Simple! Not the modern, overly complex, self-justifying-programmer convention used by Windows and Linux lol.
If it requires a certain library & version to execute - INCLUDE IT IN THE APPLICATION! It's counter to the philosophy of not reusing code, but when devs break libraries, or include 400 of the damned things, you wonder how things ever get designed in the first place. Dependency-hell (DLL-hell on Windows) is alive and well on Linux.
IMHO, when you have two screens of dependencies and libraries, you know something went wrong somewhere in development.
Why not just a single config file/folder for systemd - Why spread it out all over? I don't get it - There MUST be a perfectly good reason for it, but I can't see one, personally.
I personally don't like FlatPaks or SNAPs - The software looks awkward with it's off-kilter decoration that doesn't fit in with the rest of my system. Cludgy solutions need to be call out for what they are. Unwanted and problem causing.
I always wondered why subsystems couldn't be organised better instead of being rammed into a single folder (ie Windows, Linux AND MacOS/OSX/iOS). I also want to easily identify which actual piece of software I am using - I hate it when devs use nice names instead of the actual application name lol
How about a single, centralised system configuration application? (Windows and Linux - Again!) That would be revolutionary!
Windows development is an example of developing for someone else's requirements, presenting a cohesive, predictable environment. Step one in Linux, sometimes the hardest, is finding what caused the problem and then locating the correct forum or chat room to post the question. Then, you may be berated for not posting the right question, or having the hardware you have *facepalm*
I think one issue is referring to all Linux distros as Linux, whereas Linux only refers to the kernel, nothing else.
IMHO, if humans weren't writing the code, it might have chance to improve lol