Vorpal

Snapshots are great for solving accidental oopses, and for getting consistent backups that reflect a single point in time. But they aren't backups. If the HDD or SSD dies snapshots don't help. If the file system gets corrupted snapshots don't help. If the file data becomes corrupt snapshots don't help (since they only store a single copy of any version of a file).

So snapshots are no substitute for backups. I run btrfs and I do backups, and I sync those backups to a remote location (look up 3-2-1 backup).

Uh, this blog says "introducing", but this is hardly new. I have seen this crate around for a while, and https://crates.io/crates/crabtime/versions corroborates that.

Is this an old blog? I can't find a date on it.

Signal is pretty good.

This actually sounds like a good idea.

I strongly disagree. I'm going to quote myself from reddit here:

Why would you expect to be able to use an old compiler and new crates? Shouldn't you just pin everything to the old versions? The MSRV aware resolver (that we had stably for a year now) makes that seamless. I don't see why they expect to be able to eat their cake and have it too.

This comes up again and again by LTS fans, be it safety critical or Debian packages. Yet no one have managed to explain why they can't use a new compiler but can use new crates? Their behaviour lacks consistency.

And from a later reply:

Now if they want to fund the maintenance in question, that is an entirely different question (and would be a net benefit for everyone). But that tends to be quite rare in open source. https://xkcd.com/2347/ very much applies.

I found the discussion quite interesting over all: https://old.reddit.com/r/rust/comments/1qcxa9o/what_does_it_take_to_ship_rust_in_safetycritical/ (it is a shame lemmy is so much less active than reddit still).

I think some fixed-size collections and stuff like that would be super nice in core.

If you don't mind using a crate: take a look at the well regarded https://lib.rs/crates/heapless (but yeah, having it in core would be nice, but might be too niche).

It isn't open source, but DaVinci Resolve is available for Linux. With limited features if you don't pay. Might be overkill for what you do, and I understand it can be finicky to get it working (needs nvidia, poor support for AMD, very limited format support unless you get the paied version, ...).

I don't really do video stuff, but I did play around with it a few years ago, and it seemed very comprehensive.

I don't use Gnome, but they hate to expose settings in general it seems and like to dumb down everything (and that is why I don't use it). The issue here is that the you need KDE, Sway, Niri, Xfce, etc all to implement a setting for this. Middle mouse paste is useful and has been standard on Unix-likes for decades. There is literally no reason to remove it.

Yeah, the Flint 3 seems like a worse overall router when it comes to computational power and chipset. The only thing it has going for it is WiFi 7 (instead of 6) and 2.5 G ethernet on all ports. The Flint 3 is also more power hungry, which isn't great given the high energy costs in Europe.

Most people don't benefit from WiFi 7 (WiFi 6 is already good enough for almost everything) and if you want more than 2x 2.5G ports, consider getting a (managed) switch to extend the router with.

No, it was your assertion that a wheel being too fiddly. It seemed quite broad (stating it as an universal truth). It might be for you, but not for most people (but you wrote it as an unqualified statement).

While that works, it will use more electricity than an all-in-one ARM based router. Depending on prices and renewable/fossil mixture where you live, this may or may not be a concern.

GL.Inet products that use Mediatek chipsets are great since you can usually flash standard OpenWRT on them. I would avoid routers with different chipsets since they are unlikely to get proper support.

(Though I can't say that my MT-6000 is cheap, but it is an extremely capable router. That is top of the line though, they have cheaper stuff.)

Not true, if there is no user visible setting for it. Changing a hidden gsetting via a command line is essentially removing it since it will likely bitrot and then be fully removed in a few years.

For many people this is a non-issue. I think this a case of just accepting we are different and don't need to force our view on everyone else.

Maybe 15 years ago I had a mouse with a tilting scroll wheel (for side scrolling), on that one I did have issues with middle click, for about a month until I got used to clicking straight down.

So maybe it is just a question of practice? Maybe not. But since both options exist there is no need to get upset.