This has very little to do with "corporations deciding the internet should be a predominantly private space", and everything to do with governments deciding that the internet is open season for information warfare and spying on citizens. The big push for HTTPS-everywhere hasn't been driven by "corporations affected by thieves", it's been driven in the wake of the Snowden revelations.
As long as Advanced Persistent Threats exist, you have no way of verifying you're even reading the real c2.org, or ASCII-doc site, or some censored replacement a privileged network opponent is impersonating it with.
HTTPS gives us some measure of security that we're talking with who we think we're talking with back.
Finding so far: Yes, they will. No need to hurry, but I will go https eventually. Of the sites I checked quickly, these are running non-https by default:
http://www.tandf.co.uk (Taylor & Francis, bunch of engineering journals)
http://www.aps.org (American Physical Society, i.e. all the Phys. Rev. journals)
http://journals.cambridge.org (bunch of math and physics journals)
http://www.thomsonreuters.com (ManuscriptCentral, Scopus, the home of Impact Factor)
http://www.sciencemag.org (Science and other AIAA journals)
http://www.nature.com (Nature Publishing Group)
... and I couldn't be bothered to check more
[0] Except maybe that they publish them. :-)
[1] Except the AMS, which, in my limited experience, seems to be populated by, and perhaps even more important, in the charge of, people who Get It.
Scatter sample: https://www.techdiary.co.uk/elsewhere [1]
[1] I run this, though only keep the NE section updated just now.
Executing JavaScript from insecure http is a bad idea.[1] Especially for developers/IT admins who are targets of state sponsored hacking.[2]
>Please change your browser settings or upgrade your browser.
How about, no? There's a reason I block JS with noscript. It's not about page load speed, browser responsiveness, or ad blocking. (Although it helps in those areas remarkably) I block JS because executing untrusted JS code[3] is a good way to get hacked.
[1]http://www.metafilter.com/130629/Possible-FBI-infiltration-o... [2]http://www.infoworld.com/article/2609621/hacking/uk-spy-agen... [3]https://mazinahmed.net/uploads/Bypassing%20NoScript%20Securi...
Cookies are still harmful if no JS?
https://stormpath.com/blog/where-to-store-your-jwts-cookies-...
But that's coming from a site admin point of view. As a user, it would be great to have a browser plugin that allows me to reject cookies that aren't secure/httponly.
Think of it, all of those brilliant http://c2.org wiki's and ASCII-doc sites are now marked "insecure".
Fundamentally -- some wonderful scientists and engineers created a paradise of free exchange. Commercial enterprise introduced the concept of 'money'. A bunch of thieves robbed them. And so we all have to put up walls with locks on them.