What I am trying to point at is the vast number of users born after 1990 that have a decent basic understanding of these technologies. And within that generation, the portion that has a similar deep understanding to 1990s users is a population which by absolute size is several orders of magnitude larger what it was in the 1990s. And it is going to keep increasing.
> the proportion of technically litterate users will go up over time not down.
I take the proportion to mean "out of all internet/computer users". That has gone down. And that's the proportion that I think matters as it's what dictates the direction internet/computer technologies go. The proportion is going down, precisely because more people are using these technologies and the majority are not willing to learn as much.
arguably the web is the legacy thing for places that dont have apps, and native apps are mostly what they are familiar with.
See also the classical 2013 rant on the topic: http://www.coding2learn.org/blog/2013/07/29/kids-cant-use-co....
So long as sites that aren't using SSL are highlighted, and its not possible to spoof the browser into displaying a domain you're not looking at, I honestly don't see what benefit the typical user gets from seeing https://www.google.com vs google.com.
You may be amused, but in Europe the technical details of a car engine, transmission, breaks, etc, and how to perform a quick repair have been part of the drivers test (and was still, when I made mine). It was a three parts test, involving a technical part, a legal part, regarding rules and laws regulating traffic, and, finally, a practical test. (Similarly, understanding how analog radio works was part of high school curriculum.) This was based on the conviction that dealing with a technology also afforded a basic understanding of it, not the least for legal/liability reasons.
Analogously, just making that red "No SSL" alert "go away" may be not enough. It may be preferable, if users were to understand what this is and why it is important, what the possibles consequences are, etc, if they would be actively looking for this, if they would and could confirm the mode of their interaction. Not the least for legal/liability reasons. (Teach them first to never engage in any critical interaction unless there's a verified, secure connection as indicated by such and such icon or signal. Facilitate them in asserting this. Then put on an additional warning light, but don't replace the former by the latter. There's no "easy mode", no "My First Sony" – which was, by today's standards overly complex, anyway –, when it comes to your livelihood.)
A critical mass of people able to make informed technical decisions — which is what both business & democratic self-government require.
> We don't expect people to understand the details of how their car engine works, or how digital radio signals are encoded and decoded, why should we make it necessary that they do so for the internet?
We don't expect them to know the deep details of those technologies, but we do expect them to know that flammable gasoline powers an engine; we do expect them to know that radio signals can be received by anyone with a receiver (and a key, if encrypted).
I think the point is that Google doesn't want users to be able to parse this much information. Keep the people dumb, if you want to call it that way. Or uninformed, uneducated, whatever.
"Enter whatever you want to know or see in this field and we will do some magic so you get what you want".
That's where they want to go, no doubt about it as Google probably profits the most from technically-uneducated users of its services.