According to multiple sources, Google has decided to simplify our lives again by removing "Secure" identifier in its Chrome browser for HTTPS sites protected, by what it deems, valid certificates.
This development is very unwelcome, as I recall them trying this in one of the earlier iterations of their browser to dismay of many security professionals, when we could not readily lookup certificate data from the address bar.
For instance, in my demo lab environment, I am using HTTPS inspection by the firewall/IPS/AV/Antibot/URL filtering and Application control device. Its certificate is installed in the domain's Trusted Root Certification Authorities. Therefore browser will see it as "Valid" and is presently indicating that the site is secure. But, importantly, it allows me to easily verify if the traffic is being inspected, or if it is allowed by the exceptions in the sites categorization:
Add to this Google's implementation of QUIC protocol, which presently could not be inspected and it's payload analyzed, the unilateral initiative with certificate issuance log validation, and it feels like Google deliberately making the life of security specialists difficult.
I don't think that anyone believes the Internet (as a whole) to be a safe place. This is more about effectively communicating the relative security posture and risk of the site being visited.
Studies (Usenix, Harvard/MIT, CMU) have backed up the theory that passive security indicators are not effective. Fixing this requires being more "in your face" about exceptional concerns and avoiding crying wolf about the routine.
The original reference was lopsided in that it only mentioned what the Chrome overlords were taking away and ignored what was being added. Plenty of other sites (1, 2, 3, 4) have presented a more comprehensive picture of the happenings. Notably, In addition to removing 
Effectively, they are changing the default to warn about bad instead of praising what should be the norm.
