Are you asking whether I know these things or whether I'd like to? Or whether I'd like the freedom to make choices about these questions -vs- each of them being chosen for me without opportunity for input or insight?
I don't think it's particularly controversial to say that, for most people, independent of their level of technical knowledge, the ideal is for answers to all of your questions to be available & accessible in some way, & for there to be choice in that market.
People can choose to take simple defaults without delving into the hows & whys but I can't see why those same people would object to others having choice & transparency around those defaults.
In summary: I don't know what point you're trying to make.
You sound like you're reading things from my comments that suit your own rebuttal rather than what I've actually said.
From my first comment:
> The user of course shouldn't be required to care
from my second comment;
> People can choose to take simple defaults without delving into the hows & whys
I'm literally just arguing for choice, transparency & availability. I'm not proposing placing any further burdens on users regardless of what they want to care about.
and because this attitude has become so prevalent people now pile shoddy abstraction on top of shoddy abstraction without interest or ability to reason about what that does down the stack.
The lesson from this isn't "you don't need to care about how things work" but invest some time into going one or two levels deeper than you "need" to. If you have no idea how things work under the hood the moment things tend to break or leak you're going to end up clueless.
There are many many occasions where something is below the level of abstraction that you care about. Don't assume that because you care about a particular level of abstraction that everyone else should too.