Re:Chrome 68 will mark all HTTP sites as “not secure”
by erikj on Thursday February 08, 2018 @11:31PM
(#16337900)
The complexity of the web platform is at least party to blame for this. The specifications for HTTP, HTML, DOM, CSS, JavaScript together are gargantuan and growing even further every year. This makes the development of Chrome's new competitors and the maintenance of already existing browsers extremely expensive, and it also hinders cross-browser compatibility of web applications as every browser fails to implement the monstrous specs flawlessly in its own unique ways.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by sjellis on Friday February 09, 2018 @03:14AM
(#16338698)
We are luckier than we deserve that Mozilla exists. If it was necessary to re-implement a modern Web browser completely from scratch today, it would probably take someone with the level of commitment of Richard Stallman to make it happen.
There hasn't really been much of a span where there wasn't a de facto 900 Lb gorilla browser that threw its weight around. I think a lot of us watched this happen, but the various charts on this page are instructive:
https://en.wikipedia.org/wiki/Browser_wars
It appears that somehow the browser market trends toward an unstable near-monopoly of sorts, at least so far.
So, meet the new boss, same as the old boss. At least https everywhere is a long-term public good that they're willing to take grief over forcing. It beats some of the other unilateral changes various once-dominant browsers forced.