> Nope, just mean "not the guy that writes the webapp who needs to see if he is currently connected via HTTP or HTTPS".

HTTP currently shows "Not secure" to the left of the URL. It's still easy to differentiate.

(I do think hiding www is stupid, but hiding http vs https is reasonable so long as they're still marked differently. Ideally http should be a more noticeable error, like it is if there's any user input box, or better yet a massive error like it is for self-signed certs and HTTPS.)