News for hackers. Stuff that matters.
Re:Firefox 73 by newscracker on Tuesday February 11, 2020 @12:51PM (#22300610)
One more Firefox release, one more long list of people on HN who:

* have switched from Chrome because <...> reasons why Chrome is worse or has become worse

* have always used Firefox and never left it

* have used Firefox but have faced issues and would want to try it if <...>

What I, as a long time Firefox user and evangelist, would like to know is how we can have Firefox thrive and grow, what Mozilla Corporation is doing (or not doing) to get more funding for Firefox, and why we aren't seeing all those services that they wanted to sell to generate revenue. The Firefox team has reduced in size recently, and more money might probably help avoid such situations (or postpone them).

P.S.: Donations on mozilla.org go to Mozilla Foundation, which is the non-profit parent of Mozilla Corporation (the maker of Firefox). I do not know of any direct way for end users/supporters to fund Firefox development.

Re:Firefox 73 by ip26 on Tuesday February 11, 2020 @03:08PM (#22302250)
how we can have Firefox thrive and grow

Not that anyone is asking me, but I think the mobile browser is a limiter. No matter how much I like a given desktop browser, I like bookmark & password syncing more. Unfortunately for me I find the Firefox desktop browser is first class, but the mobile browser is not. As a result it's almost immediately ruled out.

I've never seen anyone else mention this so I might be a tiny minority.

Re:Firefox 73 by Zardoz84 on Wednesday February 12, 2020 @02:26AM (#22306691)
I switch to firefox mobile like a year ago and I find the experience far better that Chrome. Why ? uBlock-origin
Re:Firefox 73 by Miraste on Tuesday February 11, 2020 @03:29PM (#22302481)
You're not alone, Firefox mobile is practically unusable. But! For a while now, Mozilla has been putting all their development effort into Fenix (Firefox Preview on the Play Store), which has all the speed and responsiveness main Firefox doesn't, plus a better UI and general slickness. It even has limited extension support in the alpha, which should make it to the release version very soon. I've been using it as my main mobile browser for a few months now and it's great. There are still occasional bugs, but it's finally a legitimate Chrome alternative.
Re:Firefox 73 by noisem4ker on Tuesday February 11, 2020 @03:43PM (#22302623)
>Firefox mobile is practically unusable.

I vehemently disagree. With support for add-ons including uBlock Origin, it's one of the very few usable browsers on mobile.

Re:Firefox 73 by Miraste on Tuesday February 11, 2020 @04:45PM (#22303239)
I was using Firefox mobile with uBlock Origin, and I found that Chrome with no adblocking was a better experience. Page loads, scrolling, zooming, and the other interactions were so slow they counteracted the advantage.

That said, new Firefox mobile is way faster and the nightly build already has uBlock support. Best of both worlds.

Re:Firefox 73 by ATsch on Tuesday February 11, 2020 @08:54PM (#22305035)
I had extreme response time issue on my old phone. I recorded my screen, and I measured a reliable 3-5 60Hz frames between the touch indicator and the page scrolling. Chrome reliably had just 1.

Things got a bit better over time, but unfortunately the thing that eventually fixed it was when I got a new phone. Now I get around 2-3 90Hz frames, which is still worse than chrome, but far less noticeable. I have not measured "New Firefox"/Fenix/Preview yet, but it does feel like it's a bit closer to chrome.

Re:Firefox 73 by CannisterFlux on Wednesday February 12, 2020 @09:04AM (#22308867)
I'm not too bothered about ublock - I already run blokada so the worst adverts are already blocked at the network level - but being in Europe I can't manage without the I don't care about cookies add-on.

Whenever I've tried other browsers - Chrome, Brave, DDG - having to click "I accept" on every single webpage to remove the "This site uses cookies!" pop-up is really tedious. I hope the Firefox on Mobile add-ons support doesn't just start and end at ublock origin.

Re:Firefox 73 by mtrower on Tuesday February 11, 2020 @05:25PM (#22303617)
Slow? I don't find it slow at all, and my phone isn't exactly top-end; what kind of hardware were you running on?

(I don't use uBlock on mobile, but I might go look into it...)

My only complaint is that it doesn't integrate quite as well as Chrome, but I don't think that's Mozilla's fault.

Re:Firefox 73 by Miraste on Tuesday February 11, 2020 @05:48PM (#22303823)
I tried it on a Galaxy Tab s5e and an LG v35, which have last year's mid-range Qualcomm chip and 2018's high-end chip respectively. On the v35 loading was slow, and sometimes it would crash or make all my tabs blank until restarted. On the tablet it couldn't even scroll down a page without lagging. I haven't run into any other apps that do this on either device. Zooming was always laggy and a bit off--bad acceleration curves or something--enough that they've redone it from scratch for other platforms instead of trying to fix the code.

There's a reason Mozilla is rewriting the whole thing.

Re:Firefox 73 by mtrower on Tuesday February 11, 2020 @06:11PM (#22303975)
That's crazy =(

That LG v35 outspecs my BlackBerry KEYone by a good margin, and Firefox is just as fast as Chrome for me. Which is to say, snappy.

I read more details about your performance problems in another comment, and it sounds horrible; I can't imagine anyone using that. Sounds like a nasty bug, I guess..?

Re:Firefox 73 by scoutt on Wednesday February 12, 2020 @05:52AM (#22307760)
I read that Firefox cannot be used with uBlock on iPhone. For me Firefox adds nothing new to my mobile experience with Safari.

Unless I am wrong, which I hope I am.

Re:Firefox 73 by feanaro on Wednesday February 12, 2020 @08:02AM (#22308426)
Why do you hope you are wrong if it adds nothing new?
Re:Firefox 73 by scoutt on Wednesday February 12, 2020 @08:59AM (#22308828)
I hope I am wrong (or better, I hope what I read is wrong) so I can use Firefox with uBlock on my iPhone (I use Firefox on desktop).

AFAIK, you cannot install uBlock (or any add-on) on Firefox for iOS.

Re:Firefox 73 by Miraste on Wednesday February 12, 2020 @10:28AM (#22309544)
Sadly you're right. This is Apple's fault: they refuse to allow alternate browser engines on iOS, so iOS "Firefox" is really a Safari web view with some Firefox buttons on it. Chrome and other browsers have the same problem.
Re:Firefox 73 by gibspaulding on Tuesday February 11, 2020 @08:47PM (#22304986)
I agree. I'm hoping FF mobile continues to receive performance improvements, but personally I'd put up with a lot worse to avoid adds.
Re:Firefox 73 by zaat on Tuesday February 11, 2020 @07:35PM (#22304561)
Say what? It's the only browser I use on mobile for years, can't say I have faced any issue, not major issue, didn't face any issue, apart from very rare stuff that were fixed, can't even remember which.

Plugins support is lacking, that is true.

Re:Firefox 73 by Miraste on Tuesday February 11, 2020 @08:05PM (#22304732)
Really? Huh. I'm surprised other people's experiences have been so different. There are tons of forum complaints about the problems I've had. There's even an official faq about all the tabs going blank [1], which tells you to restart the browser and hope it goes away. Mozilla themselves gave up on the whole codebase two and a half years ago and started work on Firefox Preview/Fenix instead [2].

[1] https://support.mozilla.org/en-US/kb/firefox-android-display...

[2] https://www.xda-developers.com/mozilla-transition-users-from...

Re:Firefox 73 by feanaro on Wednesday February 12, 2020 @08:04AM (#22308442)
FWIW, my experience is exactly the same. Zero problems, snappy, supports uBlock Origin, does not contain Google spyware and I therefore vastly prefer it to Chrome.

When I first heard of people complaining that it is atrocious, it was as much news to me as it is to you that it is excellent in my experience. I agree it's a weird phenomenon.

Re:Firefox 73 by atonalfreerider on Tuesday February 11, 2020 @06:03PM (#22303919)
"practically unusable" is a hyperbolic statement. I use the mobile browser every day.
Re:Firefox 73 by thayne on Wednesday February 12, 2020 @12:47AM (#22306177)
I've been using firefox preview for a few months now and love it. My only complaint is that even though it is set up as my default browser android still insists on using chrome to open some things, such as results from google assistant. But that's hardly Mozilla's fault.
Re:Firefox 73 by mrich on Tuesday February 11, 2020 @03:47PM (#22302666)
What problems are you having with it?
Re:Firefox 73 by Miraste on Tuesday February 11, 2020 @04:40PM (#22303192)
With Preview or with stable? Preview has a couple of minor bugs, like radio button popups that don't go away when I switch tabs, or the "undo close tab" toast not disappearing, or downloads resulting in empty files sometimes. Annoying, but not dealbreakers and I'm confident they'll be fixed soon.

My issue with stable is that it's slow. Everything about it is slow. Pages that load immediately in Chrome take double digit seconds in Firefox. When they do load, scrolling lags my finger and jerks around, and zooming is noticeable unresponsive. The acceleration curves feel off too. On my mid-range tablet performance is so bad it gives me a headache.

Re:Firefox 73 by bash-j on Tuesday February 11, 2020 @05:31PM (#22303675)
My biggest issue with FF mobile (android) is sometimes when you open a link from a different app, it opens in an existing tab navigating away from a page you already had open. It should always open a new tab.

So I might open a link in my email app, then when I tap the back button on the phone, the expected behaviour is it will close the tab and return to the email app. Instead I'm finding it navigating back to the page that was open previously on the tab that was already open.

Re:Firefox 73 by everybodyknows on Tuesday February 11, 2020 @07:01PM (#22304333)
Try long-press on the link to get a context menu popup containing an entry "Open in New Tab".
Re:Firefox 73 by Jach on Tuesday February 11, 2020 @05:18PM (#22303560)
For my own experience, it's this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1374570

On heavier sites it's inevitable that it will crash. Years ago Chrome/Chrome Beta also had this problem (the root cause is with the phone hardware/android) but somehow they managed to catch it and not bring down the whole browser app.

I still use it despite the other main drawback (being slower than chrome beta on heavy sites, like say twitter) because I like my uBlock and tab-sync, but every so often I get so annoyed at it that I avoid it for about a month until Chrome even with basic adblocking via Blokada makes me mad enough to switch back.

Re:Firefox 73 by noxecanexx on Friday February 14, 2020 @08:50AM (#22326449)
You're not alone. No matter how much I hate chrome, I've never been more displeased by an app as I am with Firefox's mobile app. We might see a new one though based off firefox preview so hopefully I can make the complete switch soon
Re:Firefox 73 by Jestar342 on Tuesday February 11, 2020 @03:30PM (#22302492)
I'm syncd on all my devices with Firefox. Android devices and Linux devices. Plugins, bookmarks, containers.
Re:Firefox 73 by Scarbutt on Tuesday February 11, 2020 @07:42PM (#22304608)
Mozilla really dropped the ball(too late) on mobile, did they think mobile wasn't happening and it was just some temporary thing?
Re:Firefox 73 by sjwright on Tuesday February 11, 2020 @08:33PM (#22304902)
Actually the equal-and-opposite thing was more true. They picked up the ball so hard that they believed they could compete with Android with an entire Mozilla mobile operating system. A lot of effort was wasted.
Re:Firefox 73 by Scarbutt on Tuesday February 11, 2020 @10:40PM (#22305513)
Was referring to the browser, they didn't had an android or ios version until very late in the game. Maybe firefoxOS caused that delay? don't know.
Re:Firefox 73 by jamesgeck0 on Wednesday February 12, 2020 @10:06PM (#22315010)
Firefox Mobile came out in 2010 for Maemo. There were more mobile operating systems at the time, and it was less clear which one was going to win out. Mozilla lead with support for the most open option.

The Android version was released a year later, three years after (the frankly pretty unappealing) Android 1.0 release. It was within months of Opera's Android launch. Hardly "very late."

Re:Firefox 73 by CM30 on Tuesday February 11, 2020 @02:34PM (#22301831)
Fortunately/unfortunately (hard to tell which), the answer for 'how to get Firefox to thrive and grow' might basically be to spend more money on ads, since Google Chrome was advertised everywhere in its early days. At one point, they were running TV commercials and putting ads on billboards at stations here in the UK.

That probably got a lot of people's attention.

Re:Firefox 73 by pbhjpbhj on Tuesday February 11, 2020 @04:37PM (#22303159)
A few people might have heard of the parent company too, like from their mobile OS, or from the search engine where they type their addresses in when browsing.
Re:Firefox 73 by MauranKilom on Tuesday February 11, 2020 @03:05PM (#22302224)
I've seen a bunch of Firefox ads (both irl and online) over the past year after Quantum was out.
Re:Firefox 73 by latexr on Wednesday February 12, 2020 @05:38AM (#22307680)
> how we can have Firefox thrive and grow

By satisfying the needs of users who

> have used Firefox but have faced issues and would want to try it if <...>

You’re right that every time there’s a Firefox release, it rises to the top of HN with the same comments. I’ve stopped commenting, but I’ll do so now since you asked.

Gripes with Firefox I’ve seen on HN include bad midi support and lack of (or broken) support for macOS features such as the Keychain.

My reason for not using Firefox (and I inadvertently get people out of it) is that it’s atrocious for automation on macOS. It’s the only major browser without AppleScript support, and the bug report open for it is old enough to vote.

When I’ve talked to people from Mozilla about it, I’ve gotten the reply that AppleScript is a power user feature that regular users don’t care for. What they fail to understand is that power users build features for others. I have several tools that interact with web browsers that are relatively popular with non-power users. Every time they ask “can you add support for Firefox?” my answer needs to be “I’d like to, but they don’t provide the functionality”. You can be certain that several of those abandon Firefox, because they’d rather have the convenience of the tool.

You can have Firefox “thrive and grow” by giving its users what they need. It doesn’t matter how “private” Firefox is (and Mozilla has done plenty to not be trusted blindly on that regard) if people can’t use it as their daily browser.

Re:Firefox 73 by Silhouette on Tuesday February 11, 2020 @04:59PM (#22303369)
What I, as a long time Firefox user and evangelist, would like to know is how we can have Firefox thrive and grow

Probably the same as anything else: find a USP that resonates with a large number of potential users.

It used to be customisation and extensions, but it's been more than 2 years since Quantum and there are still numerous ways that my everyday browsing experience is worse now than it was before. I suspect that for a lot of people, Firefox is no longer particularly associated with being more customisable than any other browser, even if it was before.

Today I suspect the best shot for a solid USP is the privacy/security angle, which is what kept me on Firefox as my default browser in the end despite it being much inferior after 57. But the marketing for that is inconsistent and gets drowned out in all the who-cares features that Firefox keeps introducing.

Ironically, the breakage of extensions has probably contributed significantly to the loss of confidence in the security/privacy side, since it took out a lot of useful enhancements in those areas. Normal people don't understand tools like uBlock Origin, which are powerful but have UIs that make Git's look intuitive and well-designed, and in 2020 a simple, effective ad-blocker is entry-level for a decent browsing experience.

Re:Firefox 73 by commoner on Wednesday February 12, 2020 @03:44AM (#22307073)
AdGuard offers a simpler interface than uBlock Origin for users who prefer one. It's also free and open source, and includes most of the same filter lists.

https://addons.mozilla.org/en-US/firefox/addon/adguard-adblo...

https://github.com/AdguardTeam/AdguardBrowserExtension

Re:Firefox 73 by Kuinox on Tuesday February 11, 2020 @01:58PM (#22301438)
One of my coworker don't use it because some error in angular are showing up as [Object object] in Firefox, while in Chrome it show the full error.
Re:Firefox 73 by eitland on Tuesday February 11, 2020 @02:49PM (#22302045)
Might be the same as I saw.

I debugged something similar in Angular about 18 months ago, didn't have time to report it and blamed it on Google not testing in other browsers.

Re:Firefox 73 by jazoom on Tuesday February 11, 2020 @02:29PM (#22301770)
Not just Angular. My Vue app as well. I can't figure out why Firefox doesn't just display the error.
Re:Firefox 73 by bzbarsky on Tuesday February 11, 2020 @06:06PM (#22303943)
I'd love to know more about the setup here. I am aware of https://bugzilla.mozilla.org/show_bug.cgi?id=1595046 which is for cases when someone rejects a Promise with a non-Error (and non-DOMException, I suspect) object. Is that what's going on here? Or could it be the thing described in https://bugzilla.mozilla.org/show_bug.cgi?id=1595046#c5 with throwing a random non-Error object and the resulting console interaction?
Re:Firefox 73 by jazoom on Tuesday February 11, 2020 @06:13PM (#22303996)
I think it might have been the first case you described. I have only recently switched over to Firefox and that was my first debugging experience with it, so I didn't realise it was a specific case and a known bug. Thank you.
Re:Firefox 73 by terminaljunkid on Wednesday February 12, 2020 @12:02AM (#22305949)
I don't like to say this but Mozilla leadership sucks. In the light of previous layoffs, there was a discussion that the CEO, who doesn't even have a proper technical background, is getting too high of compensation. I have also heard Mozilla has become a Suits-first company lately.
Re:Firefox 73 by 3r8riacz on Wednesday February 12, 2020 @02:03AM (#22306558)
A self-hostable Firefox Accounts server + sync server would be great. AFAIK the FXA server is not self-hostable yet, only the sync which leaves a bad taste in owning your privacy.
Re:Firefox 73 by robbrown451 on Tuesday February 11, 2020 @02:41PM (#22301912)
Its lack of MIDI support is still holding me back. They've been talking about it for years. Till then I'm on Chromium, sorry. https://bugzilla.mozilla.org/show_bug.cgi?id=836897
Re:Firefox 73 by lioeters on Tuesday February 11, 2020 @06:37PM (#22304173)
Fascinating (and disappointing..) comment thread about implementing the WebMIDI API in Firefox.

The issue was reported (7 years ago) by Chris Wilson, who's been at Google working on WebAudio stuff for years and has published lots of related articles and repos. I'm a big fan. https://github.com/cwilso

There's even a comment from someone at Ableton, expressing interest and support ("testing with preliminary builds as well as providing hardware for implementers to test with"). That was 2 years ago, and no one from Firefox engaged them?! Sounds like a huge missed opportunity.

Sadly, the last comment a year ago was from a person no longer at Mozilla, saying the issue is stalled and that it's "very low priority work".

---

Edit: Aah, now I'm imagining what might have been, a collaboration between Firefox and Ableton, would have been so cool..

Re:Firefox 73 by FrankBooth on Tuesday February 11, 2020 @08:59PM (#22305065)
"The major blocker right now is security issues related to device firmware hijacking." - https://github.com/mozilla/standards-positions/issues/58
Re:Firefox 73 by sp332 on Tuesday February 11, 2020 @03:01PM (#22302183)
-
Re:Firefox 73 by robbrown451 on Tuesday February 11, 2020 @03:17PM (#22302335)
You can toggle it on but it doesn't actually work.
Re:Firefox 73 by tartoran on Tuesday February 11, 2020 @03:27PM (#22302443)
You can use chromium for MIDI support and FF for everything else.
Re:Firefox 73 by latexr on Wednesday February 12, 2020 @05:44AM (#22307711)
Most people don’t want to keep changing web browsers for every task. In particular if you do a lot of work (be it paid or a hobby) in a technology your web browser lacks, it’s less frustrating to use for everything the one that has the feature.
Re:Firefox 73 by SimeVidas on Friday February 14, 2020 @04:34PM (#22330629)
The problem is traction. Most people just aren’t aware of Firefox or know very little about it.

The solution is to partner with celebrities, the biggest ones, to make Firefox more popular as a choice for better privacy.

Re:Firefox 73 by faitswulff on Tuesday February 11, 2020 @07:34PM (#22304556)
To add to that, how would one get started in contributing to Firefox's development directly?
Re:Firefox 73 by aswan on Tuesday February 11, 2020 @10:00PM (#22305329)
There's some good information here: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_g...

If you want to jump right in and look for bugs that match your skills/interest, try: https://codetribute.mozilla.org/

Re:Firefox 73 by LeoTinnitus on Tuesday February 11, 2020 @04:51PM (#22303307)
I only left when they used to be the bloated browser that took up like 1gb of memory back in the late 00's early 10's.

Now that's normal and I've sorta acclimated for the past 3 years.