As opposed to the human-made brain melting videos?

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.

Missed opportunity to call it Muhummanoid

And once again, I am seriously questioning Apple’s privacy claims. Why else would Apple build such a moat around Safari?

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).

All software has bugs, including Linux. Some bugs can lead to security escalation. Those bugs are called vulnerabilities. Like bugs, all software has vulnerabilities - including Linux.

Your webcam can be accessed by hackers on Linux, on Windows, on MacOS, on BSD, it doesn’t matter.

You don’t have to get a dictionary that’s too old to find the definition of racism that strictly required belief of superiority. With the old definition, things like slavery and genocide would be a direct conclusion/justification a racist would make. Words evolve though. Nowadays racism still makes you a piece of shit, but it doesn’t necessarily make you literally Columbus or Hitler - and that is reflected in the dictionary as a new definition; where hatred is enough.

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.

All this, and while you’re at it, Donate!

I used to agree with this, but hearing interviews with actual victims changed my mind. This only works in theory.

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

1. Contrast. You can’t use light to make something dark.
2. In the HUDs that we do have (Hololens, Google Glass), you typically use something like DLP or waveguides. Both are pretty expensive.

There are fewer barriers with helmets because they are usually tinted.

I’m a fan of anything that keeps eyes more forwards/on the road.

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.

Switching over to the discrete GPU work in the efi/bios might help. Optimus (the driver that chooses between discrete and integrated) is known to be a steaming pile.

PipeWire wins in the feature-set game, which is why it is being preferred over PulseAudio.

According to the inventor of PipeWire, this is the wrong perspective to take. PipeWire is preferred over PulseAudio as a server, clients (apps) should continue to use the PulseAudio/JACK APIs because the PipeWire API is not designed for general use (it’s designed for things like pipewire-pulse and pipewire-jack).

The biggest hurdle to open sourcing proprietary stuff is often 3rd party code, but we can indeed hope.