I mean, as someone who hasn't encountered these same issues as you, I found btrfs really useful for home use. The snapshotting functionality is what gives me a safe feeling that I'll be able to boot my system. On ext4, any OS update could break your system and you'd have to resort to backups or a reinstall to fix it.

But yeah, it's quite possible that my hard drives were never old/bad enough that I ran into major issues...

My standard position is that GNOME is good, if you want to just use an existing workflow, whereas KDE is good, if you're looking to create your own workflow or you're fine with a mediocre, familiar (Windows-like) workflow.

But unfortunately, GNOME is really disappointing in some ways. Every so often, we have someone at work accidentally using it, because it's the default, and they always run into the same nonsense, like not being able to type a file path into the file manager, or not being able to give a name to the file they're trying to save. These are pretty bad problems that normal users are quick to encounter. It's a mystery to me, why these can't be fixed, but ultimately I just tell people to install KDE and they've all been happy about it.

Big insects are fun, too. Their method of breathing through the body surface doesn't scale, due to volume growing cubically and surface area only squarely. So, scaling them up would mean they're constantly out of breath, well, or suffocated.

The person who announced this change noted in a reply that "Negative filtering is coming soon."...

https://itch.io/post/11414056

Nope. The actual disclosure dialog is a bit more precise in its wording: https://itch.io/t/4309690/generative-ai-disclosure-tagging

I would not know that you can do this on Android, not without downloading another potentially malicious app anyways...

Implementation of the add() function is here: https://github.com/raldone01/python_lessons_py/blob/main/lib.py

Apparently, less also has a feature built-in to filter out lines based on keywords:

https://raymii.org/s/snippets/Exclude_lines_in_less_or_journalctl.html#%3A%7E%3Atext=Once+your%2Cterm (skip the first paragraph, past those three links)

Well, just a monitoring stack, like for example Grafana, would probably be more suitable for this specific task (if we're doing central hosting/collection).

Kind of my main recommendation is to use something with OpenTelemetry. It's pretty much the standard protocol for transferring logs, traces and metrics, so if you set everything up with that, then you can swap out the visualization software with less pain.
Here's a guide for Grafana + OpenTelemetry Collector: https://grafana.com/docs/loki/latest/send-data/otel/

In Rust, as far as I understand anyway, traits define shared behavior.

They're certainly the concept closest to e.g. C#/Java interfaces. But you can also define shared behaviour with enums, as Rust's enums are on steroids.

Basically, let's say you've got two existing types TypeA and TypeB for which you want to define shared behaviour.

Then you can define an enum like so:

enum SharedBehaviour {
    A(TypeA),
    B(TypeB),
}

And then you can define the shared behavior with an impl block on the enum:

impl SharedBehaviour {
    pub fn greet(&self) {
        match self {
            SharedBehaviour::A(type_a) => println!("Hi there, {}!", type_a.name),
            SharedBehaviour::B(type_b) => println!("Hello, {}!", type_b.metadata.forename),
        }
    }
}

On the flipside, Rust doesn't have superclasses/inheritance for defining shared behaviour.

I feel like this has somewhat shifted in recent years. Due to type-aware IDEs/editors being pretty much universal now, having types speeds you up in that initial phase, too. And type inference eliminates much of the inertia, too.

I feel like the Enlightenment desktop environment isn't to everyone's taste. It's definitely got some idiosyncratic design choices...