@NEETzsche
I am slowly trying to transition, but that shit is pointlessly complicated.

@LukeAlmighty I felt the same way about running wine to play vidya but that was years ago. I'm under the impression it's way easier now

@NEETzsche @LukeAlmighty
By miles easier. And you can even play with good performance.

@alyx @LukeAlmighty yeah when I tried it last was like a decade ago and it was pretty frustrating. So I settled into a strategy of just having both on bare metal concurrently, which I might stick with because I bet there are subtle imperfections even today. It's cool that things improved though

@NEETzsche
> Apt install SomeProgram. (Let's say Appache for this example)
> Done.

What do you mean done? Where is it installed? No idea. Where is the setting file for the program? No idea. Is the website inside a folder in the program? Nah you silly, it is in a completely different random folder, that it cannot even read because it's lacking permissions. What disk are these files written on? (that's the point where I have to quit. and so far, the disk question is just... why???)

@NEETzsche
And yes, I know there is some magical system to it all, but so far, it feels like all the guides are made either academic-level complicated on purpose, or just series of commands to copy-paste without any explanation.

@LukeAlmighty which program should reveal the path of program. man which for more information.

There is a system. Just learn it in tidbits, gradually.

@LukeAlmighty @NEETzsche "info coreutils" (or just check that info page online) is a great guide to the core utilities. if you just skim the manpages for each of those along with the documentation for bash it'll form a framework, then look at documentation for the filesystem layout and the various virtual file systems

@LukeAlmighty @NEETzsche >where is it installed
Use the which command. Basically it's in a directory in your PATH environment variable (you can check it with echo "$PATH" ), and soywares installed via the package manager are usually found under /usr/bin .
>where is the configuration file
Soystem-wide (applying for all users) configuration files are usually under /etc and sometimes in a directory named after the soyware. User-specific configuration files are usually under ~/.config (the tilde represents your home directory and is supported by 99.9% of soywares).

Most linux newfag guides don't cover the points you mentioned, sadly. Anyway it's not "pointlessly complicated" at all, especially considering that wincucks programs have all sorts of default install directories (e.g. programfiles or whatever in the root of your main drive, a directory named after the publisher in the root of the main drive or programfiles, or some obscure wincucks directory like everything you install from the kikerosoft store).

@LukeAlmighty @LukeAlmighty @NEETzsche as a long time Linux user, this still irritates me beyond belief. Why doest every program just put it in /etc/ (system wide) or ~/.config (user). Why do they insist to put it in /var/share/etc/fuckyou? At least Flatpak puts all the configs in the same place.
I used to be against Flatpak because they use a shit ton of space, but after I upgraded to a 2TB SSD they're no longer an issue, and I actually like Flatpak better than apt/dpkg for most user-applications.
AppImages can go fuck themselves, I hate having the "you need to update, download the new Appimage" message, it's why I switched to Linux to begin with.
Snap can burn in hell. I hate having one million /snap/ drives in df.