Wait really? I use (((triple parentheses))) quite often to indicate sarcastic emphasis on a word. Damn racists ruining my punctuation >:(

Nouveau is dead, it's been replaced with Zink on NVK.

Dead link?

In my experience, nouveau is painfully slow and crashes constantly to the point of being virtually unusable for anything. The developers agree, as in the last couple months nouveau has been phased out of Mesa entirely. More recent Mesa versions now implement OpenGL on Nvidia using Zink on NVK, and the result is quite a bit faster and FAR more stable.

If your distribution currently still ships a Mesa version which uses nouveau, I would personally recommend you just stick with the Intel graphics for now.

Based on that plus the various other mistakes, my guess is that OP's native language isn't English, but probably one of the many languages which uses masculine pronouns as gender-neutral, and they're just doing a literal translation from their native language.

Am I gregnant?

• An object at motion stays in motion
• An object at rest stays at rest
• Don't push the big red button

ext4 is intended for a completely different use case, though? bcachefs is competing with btrfs and ZFS in big storage arrays spanning multiple drives, probably with SSD cache. ext4 is a nice filesystem for client devices, but doesn't support some things which are kinda fundamental at larger scales like data checksumming, snapshots, or transparent compression.

bcachefs is way more flexible than btrfs on multi-device filesystems. You can group storage devices together based on performance/capacity/whatever else, and then do funky things like assigning a group of SSDs as a write-through/write-back cache for a bigger array of HDDs. You can also configure a ton of properties for individual files or directories, including the cache+main storage group, amount of data replicas, compression type, and quite a bit more.

So you could have two files in the same folder, one of them stored compressed on an array of HDDs in RAID10 and the other one stored on a different array of HDDs uncompressed in RAID5 with a write-back SSD cache, and wouldn't have to fiddle around with multiple filesystems and bind mounts - everything can be configured by simply setting xattr values. You could even have a third file which is striped across both groups of HDDs without having to partition them up.

While I agree that this is stupid, why would a deaf person be using Spotify in the first place?

Shame, now it won't be possible to access Gmail from the Nintendo DS Browser.