And yes, even sending an age bracket exposes the age over time as you can observe a repeat visitor changing brackets and compute the actual age from that. With the server sending the info instead you can't really tell if the browser blocked it, or if the user just didn't navigate further on the page. (The browser still need to fetch all the CSS and other resources though, otherwise that would be possible to tell apart.)

Plus I have very soft water, so all combined I can get through an entire winter with just one set of wicks.

Still, I wish they made washable wicks out of fabric instead, so you could just put it in a bath of vinegar or citric acid for a few hours and then put them in the washing machine. In theory I see no reason they couldn't last for years.

As a bonus, Hetzner is European.

Also, any metric ceases to be a good metric the moment it becomes a goal.

I have observed both of the above statements in many different contexts, they seem to be (somewhat) universal rules for human society.

You might well be right, it is not an area I know much of or work in. But I'm a fan of reliable sources for claims. It is far to easy to make general statements on the internet that appear authorative.

One thing I noticed is that if I connect to a gigabit upstream port, that the connection drops to 100 mbit/s when the computer is off, but if I connect to a 2.5 Gbit port, it stays at full speed. This is based both on LEDs on the connector as well as the OpenWRT dashboard on the router. If it made a difference it was too small to reliably measure with my simple meter.

If it makes a difference (potentially does for conversion losses I would guess), this is on 230 V mains.

And if you have your own well, you generally do a cheaper filter targeted at whatever impurity you have (such as an iron filter), rather than a reverse osmosis filter.

With reverse osmosis the water also gets too pure for drinking and you need to add back minerals to it for safety, it is not healthy to drink ultra pure water for any prolonged period of time.

The air outside is extremely dry (<5% relative humidity once heated to indoor temperatures), and the air is quickly replaced by the ventilation. I have anecdotely heard that in the US they have much lower requirements of rate of air replacement than here in Sweden though, so maybe that could work there, but then you would also have stale air, which doesn't sound great.

Again, depends on what you are doing. If you are doing web servers, electron apps or microcontrollers, sure. If you are doing batch computation, games, simulation, anything number crunchy, etc: no. As soon as you are CPU or memory bandwidth bound, optimisation does matter. And if you care about battery usage you also want to go to sleep as soon as possible (so any phone apps for example).

As usual, this depends heavily on what you do. I had written a program where Arc reference counting was 25 % of the runtime. All from a single instance as well. I refactored to use borrows and annotated relevant structs with lifetimes. This also enabled additional optimisation where I could also avoid some copies, and in total I saved around 36% of the total runtime compared to before.

The reason Arc was so expensive here is likely that the reference count was contended, so the cacheline was bouncing back and forth between the cores that ran the threads in the threadpool working on the task.

In conclusion, neither extreme is correct. Often Arc is fine, sometimes it really isn't. And the only way to know is to profile. Always profile, humans are terrible at predicting performance.

(And to quite a few people, coming up with ways to avoid Arc/clone/Box, etc can be fun, so there is that too. If you don't enjoy that, then don't participate in that hobby.)

As far as I know that has only been decided in US so far, which is far from the whole world.

It seems like a worthwhile study if you want to know what CPU to buy to play specific old games that use bus locks. Games that will never be fixed.

Not all of us are in that position, and modern font rendering has gotten really bad on non-high DPI monitors, so using a bitmap font has been a way to get rid of the blur and get back to sharp crisp text.

For me, I'd rather have jagged text than a blurry literally headache inducing mess.

That said, the issue here isn't that one is better than the other, but that for some people one or the other is easier to read, and the right answer is that all of this need to be configurable. Just like light and dark mode.

And no, subpixel anti-aliasing doesn't help, the colour bleeding is even worse.