The more time I spend with Linux the more I realize that Distro doesn’t matter, GUI doesn’t matter, experience doesn’t matter.
Distro doesn’t matter because you will inevitably come across something that you need that doesn’t work on your distribution.
GUI doesn’t matter because no matter what you do you will %100 have to use the terminal and if you can do it once you can do it again.
Experience doesn’t matter because if you’re inexperienced you have to go outside your Comfort zone, if you’re experienced you got there because you like going outside your comfort zone and you will constantly stay in that state.
WTF are you guys doing with your PCs??? I've been running Mint for over a year now and the only time I've used the terminal was to open a port for Chromecast. I browse, I game, I watch shows, etc. maybe I'm just really lucky, idk, it's been nothing but smooth sailing.
We have become philosophers of our own, as tweaking Linux has been a way to meditate our stressful mind to overcome the difficulty of touching grasses.
I personally use it to run a headless docker on fedora 40 server with containers holding jellyfin, filebrowser, pia, qBittorrent a desktop in noVNC a pfsense server, and probably some stuff I forgot.
Meh, don't worry about it. If you are happy with how it's going for you - enjoy the ride! Not everyone needs to be bothered by the terminal. But it IS there if you need it or want to use it.
Besides, if Arch users wanted to be be real gurus they'd be running EMACS and not Arch.
Same could be said for any other distro. I think his point is that when shit just works, nothing makes a difference between distro. Be it Arch, Debian, Ubuntu, Mint, Fedora, Gentoo
Not exactly advanced, but I missed the super+P shortcut when switching from desk and monitor to sofa and TV. Made a couple of one line shell scripts that call Xrandr then bound them to keyboard shortcuts.
When I was switching from Windows to Linux on my PCs (both at home and at work), I originally wanted to use Debian because I'm most familiar with it and have been running it on servers for 20+ years.
I have to use Fedora at work though - it's a lightly-modified version of Fedora that runs some automatic configuration on first boot and first log in for things like ensuring disk encryption is enabled (including adding randomly-generated secondary keys for IT support), 802.1x certificates for Ethernet and VPN auth, Chef, endpoint security, etc.
Anyways, I started using it and love it. I'm running it at home now too. I realised the difference between distros is much narrower than it used to be.
That huge chunk of learning required for arch when you've never used Linux before is really hard to imagine when you have years of experience working Linux under your belt. That does not mean it doesn't exist for new users though.
That shit's complex and long. Much as I appreciate the sentiment of "the distro doesn't matter" I really can't agree.
I wish gentoo was more explored, I felt the same way and then it finally scratched the itch of things working (perhaps even too many options). I actually ended up using gentoo because it was less of a headache to just get things to work in a way that does not feel hacky
I moved to Arch about 20 years ago because I wanted Gentoo but I didn't want to wait hours for compilation. I remember it fondly though. emerge was kind of a killer feature.
Though I gotta say, I'm a bit more curious now that we have better processors. And I'm curious what I've missed over the years.
Experience doesn’t matter because if you’re inexperienced you have to go outside your Comfort zone, if you’re experienced you got there because you like going outside your comfort zone and you will constantly stay in that state.
I was experimenting a lot during my early Linux months but then I found what works for me and settled with it. I don't leave my comfort zone much anymore.
a whistle is blown, people start running out the trenches rifle in hand. Shouting while bombs pounder around, you stay still, disoriented. The general grabs your jacket and starts screaming. You cannot figure a single word of what he says, he just puts a monad into your hands.
You end up saying something similar to yourself after you read and fail to understand a LKML archive because it's the only available documentation on this specific flag that you may or may not need and if you don't need it why not turn it off. Repeat this many times for much learning (eventually).
It was a great experience but next time I'm building everything not strictly necessary as a module.
This was my experience just setting it up as dualboot and not doing super much with it. Sure I failed installing it a few times but I came out with more understanding of file systems, and in the end the wiki told me everything I needed to know.
I installed Slackware from 24 floppies I downloaded from a Volkerdings personal server, because I didn't have a CD ROM. I installed using documentation printed on a dot matrix printer that was versions out of date.. It took a day to compile a kernel. I've had to manually patch drivers (3c509 baaabyyy).
I dreamed about a future where I never had to do that again. Arch pisses me off.
How long ago was that? I have installed Arch with archinstall on ~10 different PCs over the last 4 years without any issues. Maybe I just got lucky, though.
Archinstall works until it doesn't. Recently I tried Luks and BTRFS more than 6 times leading to a script error each and every time. Could I have done something simpler and archinstall work? Possibly. But it offers those things out of the box and for it to fail each and every time ultimately led me back to the wiki to do it manually.
I tried Luks and BTRFS more than 6 times leading to a script error each and every time.
This was actually my experience also, so I went back to a manual install to just get it done. I think the archinstall script won't get any configuration of device-mapper/LVM right (including disk encryption with cryptsetup). The disk encrypt setup had even more hoops to go through than just LVM.
Some weeks ago I tried to install Arch on an old laptop, and since it have been many years since I've installed Arch for the last time, and I've heard good things about archinstall, I decided to try it. Nothing fancy: single drive, LXQt, no encryption, auto partitioning...
I tried maybe 4 or 5 times, configuring different settings in the script, and every single time it gave me a broken installation: no GRUB, or no display manager, or incorrect video driver (Intel, no Nvidia here). I supposedly configured all the options correctly, but I never got a working system. In the end I snapped and searched for some video tutorial and installed Arch the old way. I have no desire to use that script again, at least for a long time.
Not an accurate depiction of birds...after the helpless phase birds become fledglings where they leave the nest but are still dependent on their parents for food. Social structures vary a lot by species but many remain with parents for quite some time.
I mean, some bird species have mothers that essentially drop their fledglings to predators to distract from themselves (and their insecurities), or just simply don't feel bothered to actually help raise them to maturity.
True. Some just lay their eggs in someone else's nest and go "good luck!" It's hard to characterize the behavior universally across an entire class. But I wouldn't say what's depicted here is very typical.
It's also, in my experience, very rare for passeriformes to run Arch Linux.
The fact that most people assume Arch is a broken mess because of a meme is wild. Same people would think Linux is impossible to use if they used Windows still.
Misinformation can spread like wildfire, especially in an environment, when people take someone's statements as fact, instead of evaluating anything themselves. Very easy to echo bad takes
Stable if you want stability, meaning it doesn't change often (minor updates only).
Testing if you want newer packages that have at least gone through some level of testing. They've been in unstable for at least 3-10 days with no major bug reports.
Unstable/sid if you want to assist the Debian project by reporting bugs (which is always appreciated!), or want the "breaks all the time" experience of other distros.
Debian unstable doesn't break all the time, tho. There's only been a handful of times in my 27 years of using it that something got truly borked.
(That's not counting times when two packages have the same file and there's a conflict. That's trivial to resolve once you've seen it a few times. Even that is relatively rare.)
I’ve never had Debian or Arch completely break, but have had my share of annoying bugs with both of them. Biggest issue I kept having with Debian is it’d just get stuck and wouldn’t update. Think it was 12.4 I had this problem with. Way more annoying than anything Arch did to my system. I’m using Fedora now days.
I also use Debian and Fedora on different computers so I'm curious, how do they compare in your opinion? Any interesting differences or reasons to use one instead of the other?