export PATH=$PATH:/mypath1:/mypath2 in ~/.profile. Means “add :/mypath1:/mypath2 to what is already in $PATH.” If you need the entire system to be aware, set or update it in /etc/environment with PATH=...

Absolutely. The only difference is that the benefits aren’t imaginary, they are quite tangible.

Slow chargers are really hard to fuck up, you’re good with almost anything. That being said, slow charging is 10w - so you already have what you need.

RAM could be a cheaper culprit. Try re-seating it.

Do not use Manjaro. It is a known trap. What you can do is install pamac, which is what Manjaro uses for GUI package management. It’s been a hot minute since I’ve used Arch, so here’s a tutorial:

https://itsfoss.com/install-pamac-arch-linux/

Alternatively you could look at Garuda, which is a solid Arch distro. You’ll either love or hate the theme, but that’s easy to change. It also comes with an interactive kernel by default (most distros use a regular kernel build, which works better for servers).

Whatever you do, please please please not Ubuntu. It’s the lowest common denominator. Emphasis on “lowest”. It was good in the past, but Canonical have really lost the plot.

For your use case, consider it to be a packaging format (like AppImage, Flatpak, Deb, RPM, etc.) that includes all the dependencies (including services, not just libraries) for the app in question.

Should I change this?

If it’s not broken don’t fix it.

Use Podman (my preferred - the SystemD approach is awesome), containerd, or Incus. Docker is a graveyard of half-finished pet projects that have no reason for existing. Podman has a Docker-compatible socket, so 100% of Docker tooling will work with it.

I have read on more than one occasion that Wine is becoming the “Linux Gaming ABI.” It’s no longer just about Windows. With the huge variety presented by distros, Wine is simply a nice stable target that never moves.

Try forcing it to use Proton (game properties in Steam).

The language itself has no type enforcement, the type checking is implemented within nixpkgs. This might seem like pedantry, but it really matters for things like LSPs (text editor autocomplete). I think that’s what scares some people off: it’s like OG Minecraft, you need to have the wiki/search.nixos.org open while you are doing your editing.

That being said, the type checking goes much deeper than what the windows registry does - e.g. it won’t allow you to enable conflicting services - like grub and systemd-boot - at the same time.

Apparently the upgrade (including configuration) is incredibly smooth. Those interested in tinkering with the vanilla experience have had to install it in a VM.

Nah, it’s just Linus. I have endless time for people who want to learn. Linus doesn’t want to learn, he wants to be right.

I’m 110% with you here. Debian have make it much more difficult to break your system, so it should be stack sponge proof going forward. I still wouldn’t put it past Linus to fuck it up some other way (you know, maybe he’ll curl HTML into bash instead of a script), and he’ll still stand his ground and blame the world. And then later give one of his non-apology apologies.

I used to be a huge fan.

There’s a difference between “can” and “want.” For example, OP might have been planning to watch his home vids with your mom, but couldn’t due to a rolling update.

Linus is dunning-kruger crystallized and refined. He routinely talks authoritatively about subjects he knows little about. His qubit analogy is particularly wrong and annoying, and he doesn’t stop bringing it up.

Either way, more idiot filters have been installed in front of that and you’ll have to do way more work (likely learning something in the process) to fuck your system up like that.

It does. I have it enabled and tested. “Client Device Isolation.” It’s enabled per SSID.

Ooh I like the idea of “no Internet.” I do trust all of those devices (open source), but they could still be pwned.

I had to fix an issue on my wife’s laptop. If you haven’t used it in a while, do yourself a favor and try it. It’s far worse than you think.

Indeed. UKIs are the way.

MacOS is a BSD, so go with Linux if you want variety.

I heard it in a podcast, but here’s a written source on that: https://fedoramagazine.org/pipewire-1-0-an-interview-with-pipewire-creator-wim-taymans/

The message is still to use the PulseAudio and JACK APIs. They are proven and they work and they are fully supported.

I know some projects now use the pw-stream API directly. There are some advantages for using this API such as being lower latency than the PulseAudio API and having more features than the JACK API. The problem is that I came to realize that the stream API (and filter API) are not the ultimate APIs. I want to move to a combination of the stream and filter API for the future.