cringe Arch btw femboys VS Real gentoo femcels

Why would you run -Syyu? -Syu is what you want 99% or the time.
- Noob here what is the difference?
  also why would an extra but the same character y make a difference? Is that common in the arch linux ecosystem?
  
  The y argument tells pacman to update the package list. This is so your computer is downloading the new packages instead of old ones from last time you updated it. The second y tells it to delete the old package list and download it from scratch. This is useful if pacman isn't working correctly. Maybe the files got corrupted. But it wastes more resources for the repo so it is not recommended as a default.
- Not everyone uses their computer all the time.
  
  Still no reason ... unless the repo is volatile, and potentially you have a corrupt version, a simple -Syu is always enough.
  
  Pfft, the losers 😎

Can't relate. I update compulsively every 2 hours on average.
- Real talk: so do I. Part of it is just being a computer nerd, part of it is working in IT, part of it has just been curiously testing Linux.
  I have had more stability doing this over the course of a year than I had running the monthly Microsoft updates on Windows 10. On the rare occasions something broke (usually my own tinkering and not the update process) simply reinstalling it actually fixed the problem 90%+. I know I'm preaching to the choir here, but I was legit surprised and thought I would have slightly more problems with a bleeding edge distro.
  As well, it's great to be able to just update everything with one simple command on the command line rather than having each application install an updater task that sometimes sits down in the system tray doing nothing but nagging you. Or having a program prompt you for an upgrade only to take you to the download page and make you basically reinstall the app over the old version with questionable results every time ...
- Also hard to relate. Got my Gentoo server running full auto updates every morning and then send an ntfy alert on success or failure. Haven't seen a failed update in so long (other than the occasional package that had a bad build or something once in a while).
  Back when I was fresh in the Gentoo and Linux world (Gentoo is where I started) and updating once a month, I can definitely say I ran into issues.. dunno if it's that big of an issue these days though.

Not sure if my memory is failing already but I no longer see those "Update portage before anything else" messages.
When something tries to overwrite stuff in /etc and you have to etc-update your shit... that's when things get real
- Really hate those few packages that don't give a shit whether or not you've already configured it or not...
  
  That's what the /etc/foo.conf.d/ is for :DDDDD
- Yes. Once I actually locked myself out of using sudo and then forgot my root password because I updated the stuff without looking at the content of those files
  I just had one of those portage update messages btw, so they are for sure still a thing

Meh, I used Gentoo in its literal first release off a DVD with only printed instructions for a stage one build on an old Pentium II. No internet or anything to fall back on. Learnt a hell of a lot (like don't select Firefox and Open Office and do an emerge world as your first package step after the initial boot because it took literally a week to compile with no indication when it would be done). Definitely have a soft spot for Larry the Cow but after running that setup for a couple of years I feel I've taken what I needed from Gentoo.
Would recommend it to anyone who wants to dig in and really learn what makes their system tick, but not as a daily driver. I feel for me Arch hits the sweet spot, but was happy with Debian/Ubuntu too (at least until Ubuntu went to shit with snaps).

One day maybe I'll understand why people are fine with package managers that have you sweat if you're updating whenever the heck you want rather than often and with a second pair of eyes on the news
- There are too many in the Linux dev community who cling to their old concepts, even if they are objectively worse. Hell, 99% of distros still don't even come with disaster recovery preconfigured; OpenSuse are the only ones I know where you don't need to be a professional to revert back to a working state in case something broke. This conservatism as well as elitism (nobody needs the new stuff if everyone just gets good and becomes a CLI magician, right?) in the community is holding us back horribly, and it shows.
  
  With nix it's easy to revert, if you keep your previous config. Version it with git and it's really easy.
  
  openSuSE comes with a fuck load of admin tools that I should probably learn by now, but i never needed it since it worked just fine
  
  I don't feel like that's much of an issue, new people are usually introduced to the easier and more robust options. There's nothing wrong in how other distros operate, just that the community shouldn't feel compelled to suggest them to people they can presume aren't the target audience

Isn't using a rolling distro, without updating it at least every couple of days (or even every single day) a big security risk?
- Not any more or less than doing the same on a “stable” distribution.
- My 4000 packages to be updated:
- Depends on what you have installed and your needs. It's a matter of understanding your system and knowing how to manage it.
- There is glsa-check for you.
  I daily-drive Gentoo on my main rig. A binary-repository exists now. You can still decide where you want different use-flag settings and save a lot compile time.
  Only for machines I don't actively use (servers) or rarely use, I have Debian stable installed.