As a sysadmin I have sadly encountered too many situations where a programmer thought “oh, this will never happen” to agree with you that a code construct that provides no information to the user should be used in such cases.

No, I actually meant it as in the traditional meaning of literally. As in

[lints.clippy]
unwrap_used = "warn"
expect_used = "warn"

along with a pre-commit hook that does

cargo clippy -D warnings

(deny warnings).

There are always better ways to write an unwrap, usually via pattern matching and handling the error cases properly, at the very least logging them.

There are a few very questionable things in there. Unwrap should literally never appear in production code so if your code base uses it so often that you want a short-hand syntax for it that calls into doubt everything else you wrote.

In 99% of those cases you would want it to resolve .. components though.

const expressions are evaluated at compile time and can be used in locations where you would have to otherwise specify a literal (or something that amounts to a named literal like a const value).

It is pretty shit at remembering search filters in general, e.g. the Linux platform filter or the co-op filter constantly reset for me and have for years.

Restarting a system gets it into a known state making debugging easier.

And what are you going to debug when the problem does not occur and you do not know how to reproduce it? There is a lot of information you can only gather while the problem occurs. And yes, this is from the software developer and sysadmin perspective, not from the layman perspective. I would rather spend a little bit more time on the problem now instead of having it occur again and again without getting any closer to an actual solution.

It is also a good idea for computing devices in general since not restarting means effectively restarting and finding out that the restart didn’t work properly or that you do not have all the information needed to log back in at the worst possible time, one you didn’t choose yourself. And if you do it often enough the number of updates/changes that could be the cause is significantly lower than if you keep things running for a long time before a restart.

It solves virtually none of them, it is pretty good at destroying all the evidence needed to actually fix the problem for good though.

Most likely it is going to be one of those AAA games too and they are all shit anyway in recent years.

it is not as if used PCs with year old components aren’t cheaper than new ones. The console is significantly worse here because the subscription prices do not get reduced by anything because the hardware is older.

Well, that and bikes just being inherently significantly more space-efficient so those lanes are not clogged when the car lanes are.

, it’s there to efficiently move as many people as possible, as safely as possible.

So you are saying you are in favor of banning cars from the street too then?

The hated minority being inferior but also immensely powerful is a pretty standard feature of anti-minority world views of all kinds. It is pretty much required to justify the extreme actions they want to take against the minority.

Those are not VPS specs, that is more the kind where you would get a dedicated hardware server at a hoster. Hosting your own becomes much more viable the larger your operation becomes.

IPv6 binds on wildcard addresses include binding to the IPv4 addresses.

What does ss -tlnp return? Does the process listen on any ports?

That should only affect ports below 1024.

Your two bind addresses might be in conflict with each other since [::]:5234 includes binding to the first one.

Which is why I said “on price”. Obviously that is only one of the factors but don’t kid yourself into thinking that your local server will ever be cheaper. It might have many other advantages but price just won’t be one of them.