Squiddles

Some people learn that way, but most don’t. It’s usually better to start with a working environment and work on one thing at a time until you learn enough that you’re ready to dig down another layer. Start with little mysteries and learn the structure of things and how to troubleshoot before jumping in the deep end. Having a system that’s hopelessly broken and you don’t know why or how to fix it is just likely to turn people away from Linux entirely. People don’t win extra points for suffering needlessly.

The bigger problem when running Arch is that there’s a very high gap between “the bootloader makes the kernel run” and “functional desktop system”. The installation guide will get you to the first one. For someone who’s used to Windows, even as an IT pro, learning Arch is a firehose that’s hard to drink from.

Once you’ve pacstrap’d and set up a user you reboot and start your new OS. Except you have no internet because you didn’t know you had to install dhcpcd. Fine, install that–except your user isn’t in sudoers, so you have to figure out how to get back to being root to edit the sudoers file. With visudo. Ten minutes later you’ve figured out how to find and edit the right line. Another ten to get out of vi. Then once that’s sorted you’re sitting at a terminal you don’t know any commands for with no idea how to get to a graphical environment.

You look on your phone and find a recommendation for XFCE4 as a lightweight and simple DE. Great, install that. Try to launch it, and…a bunch of arcane errors. Another hour of troubleshooting and you learn that you missed xorg, which for some reason isn’t a dependency of XFCE4. O…kay. You don’t want to have to launch it every time you boot, so you go digging and find out you need a desktop manager. Takes some time, but you finally install one and enable the service in systemd, which you have to do manually for some reason.

Finally you get to a graphical environment, and…the fonts are all weird, and unicode symbols are just placeholders. Wait, fonts. You have to install fonts. More research, but you get there. Finally you launch a browser and are delighted to find something familiar. It all works the same. Great! Let’s watch a video to make sure playback is working, and…no sound.

Okay, more research, and turns out you missed pulseaudio. Install that, start the daemon aaaand…no audio. Fine, how do you check the audio level? Ah, there’s an XFCE4 plugin for pulseaudio. Find that, install it, put it on your panel, click it and…pavucontrol isn’t installed. Whatever that is. Okay, install it and try again. Great! So, for some reason the default audio level when you install is 0. Turn that up and you finally hear sound! Hours after starting the process.

And every. little. thing. is like that. For weeks. Especially with Nvidia, and especially if you make the mistake of following a recent guide that shunts you into a Wayland environment. Every time you need to do something there are 20 options, five of which are well-documented but deprecated, the first three you try don’t work for reasons you don’t understand, then you finally find something that works well enough. Rinse, repeat, for every little thing.

And this is coming from a complete Arch stan. I love Arch. It’s my only distro these days. I’m on Hyprland, my neovim is tricked out, everything is slick, responsive, just takes a couple keystrokes to accomplish anything I want to do, and I have everything set up exactly how I want it. It took a long time to get there, though, and I’ve been using Linux off and on for over 20 years, maining it for the last 10.

Definitely second Dyson Sphere Program! I’m not at all interested in the combat (it’s optional), but now that they have that completed they’ll be updating other features too. I’m hundreds of hours in and still come back to it.

Yes, NIST now recommends against requiring periodic password changes in their official guidance document.

Broadly, I agree with what you’re saying. Totally just devil’s advocate-ing and speculating to provoke thought, so feel free to ignore. I wonder if the enormous number of games available plays into this. I can almost always dig around and find at least one 10/10 game from the last couple of years that I haven’t played which is already on sale for cheap. Comparing that to a 7/10 game that just came out at full price… I’d almost certainly enjoy the 7/10 game, but I’d spend less money and likely have more fun with the 10/10. The newness factor may not be enough to bump the 7/10 game to the top of the queue.

With so many great games available an 8/10 might actually feel like a logical minimum for a lot of people, which may influence the scale that reviewers use. If people tend to ignore games with 7- scores and a reviewer feels that a game is good enough that it deserves attention, they may be tempted to bump it up to 8/10 just to get it on radars.

Meanwhile, back in the day there wasn’t such a glut of games to choose from. And with better QoL standards, common UX principles, code samples, and tools/engines, games may legitimately just be better on average than they used to be, making it fiddly to try to retrofit review scores onto the same bell curve as older games. To reverse it, I can see how an 8/10 game released in 1995 might be scored significantly worse by modern reviewers for lack of QoL/UX features, controls, presentation style, etc, or even just be scored lower because in modern times it would lack the novelty it had at the time it was released.

Thanks for taking the time to respond, even though I was critical! Sure, I have no disagreement with anything you said in your reply. I’m also involved in hobbies where bad information can hurt people (including canning and foraging for mushrooms), and I’m obviously against knowledgeable people being removed from positions of authority in these communities. This post bolds the text about being worried that new mods may miss something that the old mods wouldn’t, which could lead to someone getting hurt. I saw that, and that a couple of early comments latched onto it as a focus. I had broccoli in a wok that I needed to get back to and just fired off a quick comment as a bit of infernal advocacy that the replacement of mod powers probably isn’t as dire as the quote makes it sound.

I mean, Reddit deserves to be punished, and there are many reasons to be upset (I personally shredded all my contributions and deleted my account in protest), but I kinda feel like the canning safety issue might be overblown. Nothing is stopping them from staying and calling out unsafe recipes with comments/in association with the new moderators. Sure, they have to go through the new mods to fully remove things, and their removal in the first place raises significant ethical questions, but calling this a safety issue because “someone else could get it wrong” seems like they’re reaching.