Meanwhile, Google saw fit to break[1] countless games, basically erasing pieces of culture / shared history.<p>I don't necessarily have an issue with dropping legacy compatibility, but you can't both drop legacy compatibility <i>and</i> disallow downgrades. There needs to be a way to access old experiences.<p>[1] <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=840866#c104" rel="nofollow">https://bugs.chromium.org/p/chromium/issues/detail?id=840866...</a>
It’s not really much of a statement. Anyone with any sense knows that the browser is the attack vector of most threats and security is probably the single most important feature of a browser today.
The conversation in the thread demonstrates why devs shouldn’t talk publicly. He clearly didn’t convince the people he was addressing, and by engaging he opened himself up to the risk of Misspeaking and causing a shitstorm. We’ll see far fewer of these interactions as more repurcussions happen.
And here I was thinking the chrome UI refresh was a breath of fresh air.<p>The car analogy was apt. If Ford updated the design of one their cars, most people would find it absurd to, in a conversation with an assembly line worker from one of the factories, demand they keep producing the older design with all of the latest safety features. I find this similarly absurd.
This seems like good advice. There are lots of reasons not to use an old version.<p>Imagine if you were still using IE 6 even though your computer was perfectly capable of running a modern browser.
And? Threats and standards are constantly evolving. You should use a current browser. If you don't want to use Chrome, use another current browser.<p>Flagged as the only reason this seems to be submitted to HN is to start an unnecessary flamewar.