You can use your own router in Germany, this is enforced by the regulation agency BNetzA. Your ISP must provide you with sufficient information to set it up.
I think it's fair to say the vast majority of users won't be able to pull that off. I doubt even half of them know what a router is, let alone that there are differences between models.
For those who know they can use their own modems, sufficient information must be available, but only a sliver of the people with AVM modems will have that kind of knowledge.
There is the class that fails at reading and adhering to IKEA instructions, yeah.
But this is something that ask the non-obvious things will get explained to you if you walk into a MediaMarkt to where modern routers are and queue in line for the area's sales person to get to you and tell you what to buy, and how to get your hands on the relevant access credentials/how to get the new one to connect to the ISP.
You're forgetting that most installs of non-ISP-provided moderns for residential Internet are set up by the tech person of the household who quite possibly never heard of what a NAS is and why they may want one.
Often the only paper manual thing in the box is literally the quick start guide that a motivated person who has what could be called "common sense" on treatment of/interaction with computing equipment. You know, the person who knows to check the plugs because they don't consider themselves above it but do know that it's one of if not the first thing they are asked if they can support.
As a point of interest, there is a class of patterns called Standard Essential Patents (SEP), which the patent holder is required to sell licenses under fair, reasonable, and non-discriminatory (FRAND) conditions when an implementation of that patented idea is required to comply with certain standards.
What is even more interesting: At a given power rating, coal plants produce up to 3 times more radioactivity than nuclear power plants directly in leftover ash because coal contains large numbers of radioactive isotopes. It might not seem like much, but when you consider that a 1TWe coal plant burns 3.2Mt of coal a year compared to 27t of uranium for an equivalent nuclear power plant, this might become more apparent.
Most of that waste is captured in ash via particle filters and has to be treated like any highly toxic and radioactive waste, but as far as I know this waste it not destined for secured long term nuclear disposal where it would be kept safe from interacting with the environment. We don’t seem to have a problem with that…
Further, some low percentage (literature tends to point at .5%) of it is in gaseous form or cannot be filtered, so it gets vented into the atmosphere. That’s assuming modern and intact particle filters. And we aren’t even talking about CO2 here.
It’s somewhat absurd we have to have discussions about nuclear power plant waste in this reality.
Nuclear power plants produce many many orders of magnitude more radioactivity than coal power plants for a given amount of energy produced. You are probably misinterpreting the famous 1978 study [1] where the radioactive emissions of nuclear and coal power plants were estimated to be roughly the same. This does not include the solid and liquid nuclear waste, only the radioactive gases that are inadvertently leaked from nuclear reactors. Coal ash is barely radioactive at all, and the radioactivity is completely negligible compared to the chemical toxicity.
Elm semantics were originally loosely based on functional reactive programming in the sense of Conal Elliot, as per the thesis of its author.
Redux on the other hand is just imperative programming folks rediscovering that a state transition can be described as a pure function S -> S, with all the benefits that come along with it. This is as old as lambda calculus itself. Words like reducer are just red herrings.
The primary problem is language/library designers/users believing there must be one true canonical meaning of the word „length“ like you just did, and that „length“ would be the best name for the given interface.
In database or more subtly various filesystems code the notion of bytes or codepoints might be more relevant.
By the way, what about ASCII control characters? Does carriage return have some intrinsic or clearly well defined notion of „length“ to you?
What about digraphs like ij in Dutch? Are they a singular grapheme cluster? Is this locale dependent? Do you have all scripts and cultures in mind?
And some clients expect that whitespace is not included in string length. "I asked to put 50 letters in this box, why can I only put 42?" would not be an unexpected complaint when working with clients. Even if you manage to convey that spaces are something funny called "characters", they might not understand that newlines are characters as well. Or emojis.
Credit card numbers come to mind, printed in letters they are often grouped into four number block separated by whitespace, e.g. "5432 7890 6543 4365" and now try to copy-paste this into a form field of "length" 16.
Ok, that's more of a usability issue and many front end developers seem to be rather disconnected from the real world. Phone number entry is an even worse case, but I digress ...
