maxhurt
Senior Member
- Joined
- Oct 13, 2005
- Messages
- 2,365
- Reaction score
- 0
Sorry for barging in, but I ended up in these parts from somewhere else after many years and thought this was an old sticky thread but turned out not
Disclaimer: (ex-)Arch developer for many years.
Don't worry, that's a concern for distros like Gentoo. Just to make it 100% clear, Arch's package manager Pacman is built primarily for "binary" packages, not "source". Compiled (source) packages is a secondary feature only. I'm not sure I've heard of anyone compiling packages aside from a few isolated cases.
It is still true that it is a challenge because of the lack of a graphical installer and (official) graphical package manager. You face the same problem with things like LFS. I think the team these days is looking forward to some future projects on that end.
Even after many years (not as many as the other old-timers of the 90s), I still have to look things up when installing and setting things up. I am shamelessly NOT using any Linux at all these days, but that's for other reasons which can also be valid for Linux in general (hardware/motherboard issues with primary machine).
Some things cannot just be committed to memory, and some things are what I call maintenance "burden". It is not without trouble, and trouble costs time. For beginners and experts alike, Arch, Gentoo, Slackware and LFS are just not efficient and productive use of time.
So by that definition, even after a decade of contributing to Arch, Linux and open-source, because I choose the path of least resistance in terms of WM/DE, I am not a 'real' Linux user
I am like this too, but unfortunately, I don't see Wayland is making things much more beautiful.
Disclaimer: (ex-)Arch developer for many years.
Hi. Any arch user? Is the task of compiling e program to suit each need daunting? Hope to try. TIA
Don't worry, that's a concern for distros like Gentoo. Just to make it 100% clear, Arch's package manager Pacman is built primarily for "binary" packages, not "source". Compiled (source) packages is a secondary feature only. I'm not sure I've heard of anyone compiling packages aside from a few isolated cases.
Arch is really not that difficult to use as a day to day user, might be diff for you depending on your need.
It is still true that it is a challenge because of the lack of a graphical installer and (official) graphical package manager. You face the same problem with things like LFS. I think the team these days is looking forward to some future projects on that end.
Even after many years (not as many as the other old-timers of the 90s), I still have to look things up when installing and setting things up. I am shamelessly NOT using any Linux at all these days, but that's for other reasons which can also be valid for Linux in general (hardware/motherboard issues with primary machine).
Some things cannot just be committed to memory, and some things are what I call maintenance "burden". It is not without trouble, and trouble costs time. For beginners and experts alike, Arch, Gentoo, Slackware and LFS are just not efficient and productive use of time.
Amateurs.
'Real' Linux users use a plain Wayland compositor + window manager like Weston or Sway and write their own config files to beat it into submission. No legacy Xorg DEs or WMs .
So by that definition, even after a decade of contributing to Arch, Linux and open-source, because I choose the path of least resistance in terms of WM/DE, I am not a 'real' Linux user
But I do want a slightly beautiful interface.
I am like this too, but unfortunately, I don't see Wayland is making things much more beautiful.

