Re: Not as disruptive as it sounds
"Consistently insecure content – files served via HTTP from HTTP websites – are not affected by this change (users will still see the "Not Secure" omnibox badge in that case)"
... that is, so if your server (embedded or not) is not serving HTTPS and only plain HTTP, then there is no impact.
IMO this will have the largest impact on corporates which put SSL accelerators before their CMS, but skimp on the same security for the static content. It is an infuriating habit and I will be glad to see it gone.
Biting the hand that feeds IT
