5 ms·
Unfortunately, Chrome 70 is also when `www` subdomain is slated to get re-hidden, and when web audio breaking changes are slated to get re-introduced. There's
by danShumway 8y ago
Unfortunately, Chrome 70 is also when `www` subdomain is slated to get re-hidden, and when web audio breaking changes are slated to get re-introduced.
There's just too much to keep up with at this point.
I'm happy about this change, it's a big move in the right direction. But it doesn't give me any confidence for the future. It's crazy that users have to do this every single release. It can't continue like this.
I have no idea anymore what it would take to get me to switch back to Chrome or to start recommending it to friends and family. I feel like Google is actively training technical communities to distrust them. It's going to turn into some kind of Pavlovian response.
- umanwizard 8y agoA Google representative has claimed on the domain hiding bug report that the change is shelved due to the feedback. Edit: Permalink to the relevant comment: https://bugs.chromium.org/p/chromium/issues/detail?id=883038#c60 https://bugs.chromium.org/p/chromium/issues/detail?id=883038...
- danShumway 8y agoHas it been shelved from Chrome 70? The last that I heard, it was temporarily removed in Chrome 69, and `www` would be reintroduced in 70. Unless things have changed again since then, `m` was the only change that was actually shelved.
- umanwizard 8y agoSee my edit. They have confirmed it is not going live in 70.
- danShumway 8y agoNice! I'll be honest, I did not expect them to reverse course on that. That makes me a bit happier about this whole thing.
- deleted 8y ago[deleted]
- AsyncAwait 8y agoBut it looks like it's going live post M70, is's not dead.
- p1mrx 8y agoToo bad there wasn't enough feedback about http:// http:// and https:// https:// hiding to make any difference. The biggest problem is that the two are hidden differently.
- ken 8y agoYes, I think that's exactly what danShumway meant by "users have to do this every single release", i.e., give feedback about a big upcoming change that should never have been made in the first place. One week it's the domain hiding, another week it's cookie clearing. Who knows what Google is planning to change next time? It's not sustainable for us to go reactive every month. There's an awfully big disconnect if the makers of the world's most-used web browser are routinely trying to change it in ways that users force them to immediately revert. That's not what good stewards do.
- Lio 8y agoI feel this attitude of “just do it and see if enough people complain” is inherent in these big web companies. Just look at how they do product naming. How many times have we seen Google or Facebook launch projects with the same name as an existing project and just use their size to steamroll over refernce to the existing work? E.g. the Go programming language or Facebook’s Flow checker for starters.
- SquareWheel 8y ago>Who knows what Google is planning to change next time? It's not exactly a secret. Go download Canary and see what's in the pipeline.
- AsyncAwait 8y agoYou missed paren't point. It's not about if you can see the changes immediately in the next release, it's that you have to be constantly vigilant as to what they're going to do next, like looking over your shoulder. You can do that, but it's time consuming and exhausting. You're better off switching browsers.
- SquareWheel 8y agoThat's overly dramatic. Both Chrome and Firefox are excellent browsers, and are developed in the open for all to see. They are examples of open source done right.
- walterbell 8y agoThe URL hiding change is NOT reversed or shelved, only delayed: > Thanks for the feedback so far. We plan to collect additional feedback, particularly about the enterprise use case, before launching the feature. We will not be launching the "www" elision in M70. Note: “before launching” the feature post-M70.
- umanwizard 8y agoMaybe it’s just a vocabulary quirk — to me, “shelved” implies “postponed indefinitely, but might come back someday”, not “cancelled forever”. So it is “shelved” according to how I understand that word. As you correctly point out, it’s not necessarily cancelled forever.
- walterbell 8y agoLaunching in M71 (i.e. delayed by a single release) would remain consistent with the Google statement. The statement applies to any delay within the range of "soon" and "not forever".
- umanwizard 8y agoYes, I agree with you. What was unclear about my comment?
- walterbell 8y agoWe also need to avoid situations where a positive reversal/fix distracts people from the introduction of a new problem, like URL display changes related to AMP.
- zavi 8y agoIt's not targeted to technical communities. Chrome's market share is 50% and growing. It became successful in the first place because it's fast and simple. It's clearly targeted to average Joe by design, not programmers.
- danShumway 8y agoA couple things: Many of the complaints that Chrome has gotten are not specific to technical communities. People were mad about `www` not because the technical communities have a thing for seeing the subdomains, but because there's a risk that average Joes can be phished when they're removed, and because on some domains the removal makes technical support for people like Joe harder. Similarly, the Web Audio complaints were not merely that the technical community wanted more control, it was that the changes broke the web for non-technical users in a way that commercially advantaged Google's own properties. Secondly, Google's external PR has never taken this stance. Google invests a lot into interfacing with the dev community and positioning Chrome as a dev-friendly browser. I very much doubt that any Chrome dev on Twitter would agree with what you're saying. They would say that Chrome is trying to be a browser for both casual and advanced users. As long as Google advertises Chrome that way, I don't see the problem with the technical community demanding a certain level of consideration. How many people on HN use Chrome (or at least did a week ago ;))? If Chrome isn't designed for people like them, than it seems like the obvious solution is for any tech savvy communities to en masse switch to Firefox and do the majority of their development/testing there. But again, most of the changes that people are mad about aren't tech-specific concerns. I don't use Chrome for daily browsing; I'm mad that Google made a change that made it easier for them to spy on my parents. I'm responsible for protecting them. I'm responsible for mitigating Chrome's technical problems when they impact nontechnical users and customers that I care about.