Live data from Hacker News

Product Updates Based on Your Feedback

blog.google

271–280 of 475 posts

Re: Product Updates Based on Your Feedback

#271
post #255

Earlier quoted context omitted.

You seem to be looking at the choice of opt-in vs. opt-out from the perspective of a user who actually cares about the feature. Much more common, though, I'd say, is the type of user who will accept whatever the default is, because they just don't care . Compare: the organ-donor registry. When it's opt-in, most people don't opt in. When it's opt-out, most people don't opt out. Most people just don't care. If you thin…

> Compare: the organ-donor registry. When it's opt-in, most people don't opt in. When it's opt-out, most people don't opt out. Most people just don't care. Most people don't know it exists or that they have an option. You cannot care about something if you don't know it's there.

> Most people don't know it exists or that they have an option. You cannot care about something if you don't know it's there.

Most people won't know that these chrome features exist. Most people don't go digging through options and settings, they just download chrome and go, go, go.

Re: Product Updates Based on Your Feedback

#274

Earlier quoted context omitted.

Did it ever?

I'm the last person to defend google, but in the beginning a reasonable argument could be made that what they wanted was better performance of javascript and website rendering in general. Microsoft, Mozilla and Apple were the only engine developers in town. Two were the default on their OSs and Mozilla was the choice of those who made a choice. So there was no real incentive to compete on performance. Chrome was intr…

Google used to pay people working on Firefox, including the lead engineer at the time, Ben Goodger. They pulled them to work on Chrome. Had they wanted, they could have invested more in Firefox to improve its performance. But what they really wanted was full control over their own Web browser.

Re: Product Updates Based on Your Feedback

#275
Won’t change my mind and will stick to Firefox after having switched because of this. First I don’t want to be logged in in my browser at all. Second, and probably more important, software is about trust. Even for an open source project, no one has the time to review millions of lines of code. So unfortunately one has to rely on what one believes is the behavior of the authors of the software. And what google did is to shatter that trust by sneaking that change discretely.

Re: Product Updates Based on Your Feedback

#276
post #255

Earlier quoted context omitted.

> Glad to see they are listening to user feedback and reacting quickly. I consider an opt-out as paying lip service to the feedback. Clearly they feel the default is more important than the generated angst. Reaction clearly needs to be even stronger to affect real change. An opt-in (e.g. a dialog on next Google login from Chrome asking for feature enable) is a compromise, an opt-out is to appease the temporarily upse…

You seem to be looking at the choice of opt-in vs. opt-out from the perspective of a user who actually cares about the feature. Much more common, though, I'd say, is the type of user who will accept whatever the default is, because they just don't care . Compare: the organ-donor registry. When it's opt-in, most people don't opt in. When it's opt-out, most people don't opt out. Most people just don't care. If you thin…

It’s not just that the user doesn’t care. I don’t want to have to monitor constantly hackernews to find out what new invasion of privacy google will sneak in discretely, even if there is a switch somewhere to opt out. I want to be able to rely on the tools I use.

Re: Product Updates Based on Your Feedback

#277

Earlier quoted context omitted.

The article says that is exactly what they are going to do now: when you clear all cookies, you will be signed out.

What they are going to do. As currently released, it is a real issue, not some misunderstanding.

Several people who make a lot of money figured it was a good idea.

Re: Product Updates Based on Your Feedback

#278

Earlier quoted context omitted.

Steps to reproduce: 1) Pick a rMBP. Any one. 2) Set display options - "more space" under System Preferences. 3) Run Firefox. Load any website. No extensions; safe mode doesn't matter. 4) 100%+ CPU, fans kick up and run high, system gets hot and slows to a crawl. Chrome and Safari run totally fine under the same conditions. It's documented pretty thoroughly in the first Bugzilla link I posted; the second one is an off…

1) I'm running a MacBook Pro (Retina, 15-inch, Mid 2015) 2) My display options are set to "more space" 3) I loaded this hackernews thread. 4) Firefox and it's child processes are using If I aggressively scroll this page I can push the cpu usage up. We have a variety of fixes in the pipeline that will help with this ( https://bugzilla.mozilla.org/show_bug.cgi?id=1429522 , https://bugzilla.mozilla.org/show_bug.cgi?id=1…

I also have this problem, and it's a reason not to use Firefox for me. Maybe you only have 4.7% of users on MacOS precisely because of problems like these?

Re: Product Updates Based on Your Feedback

#279
post #2

Like Eric Law[1], I felt like while there were some rough spots in the UX for the Chrome login and sync features, the issue was very overblown (I'd feel very differently if sync had been enabled automatically). I don't have much more to say than Law does --- except maybe that when your arch-competitor is speaking out on your behalf , maybe the narrative has gone a little haywire. I figured Google would do something c…

The sync thing was overblown. The cookies thing was a bit more concerning to me. Not so much from a privacy angle but from more of a 'Chrome has lots its way' angle. A lot of our software's more complex interfaces are Chrome-first since its faster to develop - yesterday was the first time I made a serious consideration to change that approach. Glad to see they are listening to user feedback and reacting quickly.

[deleted]
Post reply on HN