I think you keep missing my point. This isn’t about a “usual web form”. You aren’t entering your address or something. You’re configuring a service or server. Those are very different worlds. I understand that those kinds of forms where you enter your address (or whatever) wouldn’t ever have a default in there. In that context a default doesn’t make any sense (default name, default street, default city?). And even in the cases where it might, it would be - as you pointed out - unexpected for the kinds of users that usually fill out “web forms”.

When you’re configuring a server/service, that’s a very different world. Many fields could have defaults, and you wouldn’t want to hard-code those into your config. That is what this is. It’s essentially a web interface for a config file, which often has default values for any field you don’t specify for a variety of reasons. Defaults DO have special meaning here. That’s the whole point I’m trying to make! In that world it very much makes sense. The best way to show it is obviously a matter of personal taste, I actually like (and prefer) the greyed out way for reason I mentioned above.

Being shown what’s the default isn’t the same as having it actually in the field. For example the default might change, then these values would change with the default. There are also cases where they are inherited or something similar, where the upstream value isn’t as fixed as defaults normally are. So there is a functional difference to showing you a greyed out default and actually having that default be in the field.

Especially for things that essentially are a web interface for a config file where the config file gets larger with values that aren’t needed (this includes both NPM and Proxmox, as examples). Instead of like 3-4 lines it could now be like 20. It also becomes unclear when looking at the values later if they were actually set to that value intentionally or if it just happens to be the default that got filled in because some UI was used that filled all fields with their default values.

Showing the default outside in a label or as a tooltip-hover is an option, but has implications for the space needed and readability. And this way is actually much clearer if you want to look over a config and you need for example the default port or something, it’s in the exact place you expect it, shown in grey to make it clear that it wasn’t set intentionally but that it’s just the default. In some UIs there’s room for defaults, in some not. I personally vastly prefer them to be shown like this, as you might have guessed already.

Yea I realized that only after. I agree it’s slightly different from the grey text in text fields, but it still illustrates the point because it’s also an implicit default value (that happens to be unchangable in this context). So it kinda applies, but yea not quite the same.

I’m coming from the perspective of administrative interfaces, not generic forms. See my other reply for the examples that I use daily that made me have a different “intuition” here. Edit: But the fact that I got three replies in like a few minutes also shows that my perspective might not be the universal one. Still, I think it does hold up in the context of administrative interfaces (which is what NPM is).

always […] why would it be an implicit default?

Cause that’s what I intuitively expected, because in the tools that I use daily, that how it is there. Here are some examples of other administrative web interfaces that use grey to show you the implicit default that I happen to have running and could find in like 3 minutes. So much for your overconfident “always”:

• Proxmox PVE or PBS. Basically every dialog. Example network interface configuration:
• TrueNAS, example “Add Dataset”
• OPNsense, example “Firewall Rule”, the destination port range has an implicit default and is grey:

Note: I’m not talking about a form to fill in your name with “john doe” or whatever, and even that I can’t even remember seeing either. Cause it just says “Name:” and nobody needs an example.

80 being grey suggests it’s the implicit default, not an example. Like in any other input mask like this. That is a very reasonable company and not intuitive at all.

You don’t need to hard update your IP every 5 minutes. The typical DNS updaters (just use ddclient) can simply check if your IP is up to date and only update if it isn’t.

ARC is the in-memory cache used by ZFS. If it’s completely off the effect can be dramatic. Under no circumstances should a larger cache cause anything to get slower, ever. Even the raspi didn’t have memory that is that slow that this is a reasonable outcome. By default on most distros, ARC size is capped to 50% of physical system memory. Keep in mind it is a cache: if something else needs needs the RAM, it will be released.

As a concrete example: I was recently working on a server where a maintenance task that should take like 12hrs or so at the worst somehow took 2 weeks (!) and still wasn’t finished. That was ARC being disabled.

What size is the ARC set to? I’ve seen cases where it was fully disabled, which (unsurprisingly) seemed to murder performance and is probably even worse when in such a CPU limited platform. You stating that only 1.5 GB of 16 GB were in use makes this seem likely.

In general, if you care even remotely about performance, a raspberry pi is probably the wrong choice for a NAS. Even a single disk should have no issues saturating a 1gbe link. That being said, even a pi should manage 1 GBit/s on ZFS, especially when reading.

ZFS, specifically RaidZx, can be expanded like and raid 5/6 these days, assuming support from the distro (works with TrueNAS for example). The patches for this have been merged years ago now. Expanding any other array (like a striped mirror) is even simpler and is done by adding VDevs.

I’ve had nothing but issues with NC instant upload, and stopped using it. It’s error prone and needs constant hand holding for no good reason. It didn’t handle taking a picture and then deleting it instantly very well (and will throw your notifications at you for this, often more than 1). When you have limited connectivity it will utterly confuse itself and ask you to resolve conflicts for 100 files for no reason, when it could just checksum server and client files and notice they are all the exact same. Also when set to only upload on WiFi, and not being connected to WiFi it often still spams notifications that the “upload failed”, despite not being supposed to upload anything. And btw. it could upload files just fine, they failed only because upload on mobile is disabled!

It’s a nightmare. Commonly also referred to as a cluster fuck.

It really sounds great, but I’ve also read that the law contains zero directions/rules on prices for the replacement parts. So you might be able to get a replacement battery for your 200€ phone, but having to pay 200€ for it.

I man I hope not, and maybe not every company will go out of their way to follow the most malicious interpretation of the law they can (competitors might not, it’s still a somewhat competitive market).

Doing the calculation isn’t hard. It’s harder to know how much energy (be it electricity, gas, or whatever) you actually use. It also varies wildly with meals, as some need multiple stove tops (is that the right term?), possibly for varying lengths of time and/or the oven.

Please note that you can not really deduce the energy consumption from a power rating, as those usually are max values and not what it’ll actually need.

I have good enough energy monitoring that I can measure the usage (sort of), and having rather high electricity cost at around 0.40 €/kWh I do pay some attention to it. Running the oven for like an hour will be roughly 1€. Boiling water for pasta or something is probably more like 20 ct (includes cooking the pasta). Just using a lid actually helps a lot here if you make use of a lower power setting after reaching a boil and putting in the pasta.

It’s gonna have to be a very elaborate meal to break 3€. So while it does matter and add up, compared to buying fully prepared food from a restaurant, it isn’t that dramatic even with very high energy prices like these.

Cooking appliances use a lot of power, but they don’t run for whole days at a time, so the energy used also isn’t that dramatic. There’s a relatively recent video by technology connections that goes into detail, and might be of interest (link).

I just saw this post but didn’t look any further into it than reading the title.

Switching is possible now, if you want. CoMaps builds have been released for a while, and are in f-droid I think since today? I have no idea about Google play store.

If you’re happy with osmand there’s no point to switching IMHO. It’s a much more simplified interface, so customization especially compared to the enormous options in osmand are relatively limited.

That being said it does work just as well, judging from the little use I’ve had.

I don’t know a single person who graduated “on time”. This may differ from country to country, but here the nominal times are just waaaay unrealistic. I’m sure it’s possible, but at least for me I would’ve missed many opportunities, and I’m glad I took the time.

The direct shortcut for opening task manager actually also had special handling for problematic situations. This includes low memory and high CPU.

I’ve had situations where the direct shortcut worked, but ctrl-alt-delete didn’t. Never had the opposite.

Ctrl-shift-esc opens task manager directly.

It doesn’t affect refurbished computers. It doesn’t affect used computers. And all those still run windows 10 and 11 just fine. You’re just not allowed to sell a windows license pre-installed on new computers with these old processors anymore.