Live data from Hacker News

Firefox 62.0 Released

mozilla.org

181–190 of 275 posts

Re: Firefox 62.0 Released

#181
post #149

Earlier quoted context omitted.

Creating XUL, really? You cannot create an restricted API for everything, the very point of extensions, plugins, addons is community is always bigger than your developers team, and much, much more diverse. The 'long tail' effect is what extensions community is about, not '90 per cent of users'. 90 per cent of users might need just a couple of the same extensions, the other 10 per cent of users need a thousand of diff…

You can't create a UI that makes everyone happy either. For example, extensions that use the tabs WebExtension API are significantly more varied than the removed Panorama feature.

> You can't create a UI that makes everyone happy either.

That's why every software project having a user community has theme support.

Re: Firefox 62.0 Released

#182
post #13

I'm a die-hard Firefox fan. While all my colleagues develop in Chrome, I'm the weird one who uses Firefox and always catches some problem in rendering when testing. But recently I installed an 4K monitor. I use the Latest Windows 10 and have an GTX 1050 graphic card. The Firefox on this resolution is VERY slow. I have no problem in Edge or Chrome. Please, if any dev is around, check this use case.

Exactly! Firefox is very rough and slow compared to Safari on my 2016 MacBook Pro, with or without an external 4K monitor. I'd like to use Firefox, but I tend to just open Safari instead because it just feels better.

Re: Firefox 62.0 Released

#183

With all these posters complaining, am I the only one who is totally satisfied with Firefox? I never had many issues using firefox. I did use Chrome briefly, but came back to firefox. If it matters, I mostly use firefox on Debian Linux and am also not a web developer.

It's a little hard to believe a Firefox power user over any real length of time would be totally satisfied with it; they've been ripping out much-loved features right and left and stuffing it with mandatory sponsored add-ons. Still, it doesn't force report megabytes worth of data per day to the mothership, unlike Chrome...

I wasn't aware that Chrome did that, but I'm generally wary of Google anything and always have been. I'm a longtime Firefox(/DDG) power user, since it was Phoenix. I never left even when Chrome was hot, of course I've done testing on and off over the years but was never impressed with Chrome. I'm one that if just accepting anything, would use a platform's native browser (Edge, in my case) before Chrome, as native browsers have performance/power advantages due to their non-crossplatform nature.

I'm not happy with the changes they've been making but it's still the best browser by a longshot. If you're just taking defaults, Chrome is acceptable but it's not flexible enough for me.

Even with the bad decisions (removing native RSS support was a huge blow for me), Firefox is still better than it's ever been. They need to be careful though as paradoxically as it is, they're also on a knife's edge of ruining it with the face of that being this Pocket thing.

Re: Firefox 62.0 Released

#184
post #144
post #132

Earlier quoted context omitted.

That's how I expect Google to make decisions, not Mozilla. I would like to say that I trust Mozilla to appropriately weigh pros and cons and make unpopular decisions when necessary, but it seems like the entire deliberation process was a few individuals in one of the bugzilla threads that jaas linked above: https://bugzilla.mozilla.org/show_bug.cgi?id=1402890 (and I don't see any mention of how widely used it is, fro…

> That's how I expect Google to make decisions, not Mozilla Exactly. There is no point to compete with Google for "browser for Uncle Joe", Google won that battle. The power user browser niche is what Firefox could take instead. But no, let's chase after the leader by his rules, look at how good is Blackberry doing.

> Exactly. There is no point to compete with Google for "browser for Uncle Joe"

Yes there is.

For Firefox to be useful, websites need to work in it. That means web developers need to test in it. And that means that the demographics that they target need to have enough Firefox users to justify testing it. That means there needs to be a sizable portion of Firefox users in every major demographic.

Otherwise it'll be right back to where we were with IE6, except unlike back then, Google Chrome isn't abandonware that just happens to ship with Windows.

Re: Firefox 62.0 Released

#185

Earlier quoted context omitted.

From https://firefoxgraphics.github.io/telemetry/ : Linux users are about 2.7% of Firefox users Windows users are 93.2% of Firefox users 27.7% of Windows users don't have Direct2D That means 25.8% of users "run windows on hardware without decent graphics hardware". So it's entirely reasonable to prioritize these 25.8% of users over the 2.7% on Linux.

How many Linux users disable telemetry collection vs windows users (who are most certainly used to spewing telemetry to external parties)? I definitely disable it on all of my (Linux) systems where I run Firefox. I suspect I am not alone.

If you disable telemetry and then complain firefox is not prioritizing developing firefox for your system, don't be surprised if your complaints fall on deaf ears.

Re: Firefox 62.0 Released

#186

Earlier quoted context omitted.

How many Linux users disable telemetry collection vs windows users (who are most certainly used to spewing telemetry to external parties)? I definitely disable it on all of my (Linux) systems where I run Firefox. I suspect I am not alone.

If you disable telemetry and then complain firefox is not prioritizing developing firefox for your system, don't be surprised if your complaints fall on deaf ears.

Please point out where I was complaining about firefox not prioritizing development for Linux. Thanks.

Re: Firefox 62.0 Released

#187
post #140

Earlier quoted context omitted.

I've read somewhere that Firefox telemetry showed that hardly anyone used the bookmark descriptions. In that case, understandable they chose to remove them.

> I've read somewhere that Firefox telemetry showed that hardly anyone used the bookmark descriptions. > In that case, understandable they chose to remove them. It's not understandable. That logic leads to dumbed-down, point-and-grunt products because the "telemetry" shows most users aren't power users. Anyway, how much effort does it really take to maintain a text field on a bookmark entity?

>Anyway, how much effort does it really take to maintain a text field on a bookmark entity?

My thought too! Legacy extension APIs are one thing. An extra DB column / key:value pair is nothing.

Re: Firefox 62.0 Released

#188

Earlier quoted context omitted.

If you disable telemetry and then complain firefox is not prioritizing developing firefox for your system, don't be surprised if your complaints fall on deaf ears.

Please point out where I was complaining about firefox not prioritizing development for Linux. Thanks.

This comment chain is about Mozilla prioritizing a windows thing over linux / wayland work.

You're commenting in defense of the original comment, so while you didn't explicitly complain about it, you implicitly supported the complaint.

Re: Firefox 62.0 Released

#189
post #13

I'm a die-hard Firefox fan. While all my colleagues develop in Chrome, I'm the weird one who uses Firefox and always catches some problem in rendering when testing. But recently I installed an 4K monitor. I use the Latest Windows 10 and have an GTX 1050 graphic card. The Firefox on this resolution is VERY slow. I have no problem in Edge or Chrome. Please, if any dev is around, check this use case.

Exactly! Firefox is very rough and slow compared to Safari on my 2016 MacBook Pro, with or without an external 4K monitor. I'd like to use Firefox, but I tend to just open Safari instead because it just feels better.

I’ve read in places that using the “More Space” options for Retina Displays (essentially any higher resolution than the default), causes Firefox to slow down. I was in the process of moving from chrome to Firefox and realized mine was slow and I read some responses indicating what I mentioned above. I abandoned the effort then and there. It was unbearable.

Re: Firefox 62.0 Released

#190
post #91

Youtube on Firefox for me is awful. I get constant buffering on 1080p+ content. Chrome is flawless. I have the same extensions on both browsers, curious if anyone else has experienced the same recently?

There was an article on HN about this recently. I'm on phone so can't search easily, but something about it using a polyfill for a chrome specific feature. There was a way to get the old behavior in the article I think.

You install the "YouTube Classic" Firefox extension to force YouTube to use its old (non-Polymer) layout. This extension won't help with video buffering issues, however.

https://addons.mozilla.org/en-US/firefox/addon/youtube-class...

Post reply on HN