News for hackers. Stuff that matters.
Re:State of web browsers in 2018 by adimitrov on Thursday December 06, 2018 @10:51AM (#18619022)
Firefox for mobile is an excellent browser, and the only one I use. It supports extensions, such as uBlock without rooting the phone. The user interface is good, the browser is responsive and reasonably fast. Honestly, I don't know why people aren't using it.

I think most people just don't care, and just use what the system provides. As Google gets more invasive and evil, I hope that people will start to care, and Firefox and other browsers start to flourish again.

Re:State of web browsers in 2018 by SamWhited on Thursday December 06, 2018 @11:05AM (#18619168)
> I don't know why people aren't using it.

Like the article said: no one cares (more or less) about how good the browser is. If you have to go install a new browser, that's more work than just using the builtin one, and Google can force every Android phone to install Chrome out of the box.

Also, though I use Firefox mobile out of a desire to not be a part of the Chrome problem (even though I know it's useless and I'm not actually helping by doing so), it's not fast, and it's not nice to use. It's painfully slow, crashes much more frequently than the other browsers, has confusing settings and constantly promotes garbage like Pocket (which you can disable if you dig through the confusing settings, but you can't actually uninstall it), etc.

Until Mozilla gets the performance problems under control (and they're finally attempting to do this with Quantum et al.) they won't stop the bleeding. Unfortuantely, stopping the bleeding is the easy part: getting new users is the hard part and I tend to agree with the article that they don't have a way to do that on mobile (though I know nothing about marketing, so hopefully I'm wrong and just spouting nonsense here).

Re:State of web browsers in 2018 by CWuestefeld on Thursday December 06, 2018 @11:24AM (#18619370)
Until Mozilla gets the performance problems under control

Performance is 1/2 of the reason that I prefer Mozilla. As one of those people that typically has 50-100 tabs open, the Firefox model for memory management is vastly superior.

The other half of the reason is TreeStyleTab, again because I'm one of those zillion-tab users. Vertically-stacked tabs in a sidebar is the only way to manage that mountain of tabs - horizontal at the top just doesn't work. And Chrome doesn't have any extensions that support this.

Re:State of web browsers in 2018 by SamWhited on Thursday December 06, 2018 @11:37AM (#18619513)
That's actually really interesting; I don't tend to have a ton of tabs, but coworkers always told me Firefox did a terrible job with 100+ tabs and that Chrome worked better. This always made sense to me because of the multi-process architecture of Chrome, but I've never seen it myself.

So you're suggesting that Firefox actually performs better now? Maybe all my coworkers complaining about it are just repeating lore that no longer exists?

Many tabs aside though, I still have a lot of performance problems with Firefox (although it's getting better; Quantum was fantastic, I was getting really fed up with Firefox for a while before that).

Re:State of web browsers in 2018 by wvenable on Thursday December 06, 2018 @12:10PM (#18619864)
> This always made sense to me because of the multi-process architecture of Chrome, but I've never seen it myself.

If you have hundreds of tabs in Chrome, you'd have hundreds of processes. In this case, Firefox used to perform much better with lots of tabs because it didn't spin up a process for each one. The downside of this model is that a crash would take down all your tabs in Firefox rather than a single tab in Chrome. Of course, now Firefox is also multi-process.

I can never have hundreds of tabs open in Chrome because the UI just doesn't handle that nicely. In Firefox I use multi-row tabs and can comfortably have 40 tabs open without issue.

Re:State of web browsers in 2018 by Semaphor on Thursday December 06, 2018 @01:29PM (#18620671)
I don't understand how anyone can claim FF is faster. I love FF and I switched completely from chrome. But Chrome is far faster. I don't know maybe it is because I have an abundance of RAM (32 GB) and others don't and that's why they think FF is faster.

But for me, it's easy to test. Go to http://addic7ed.com/ and open the (very long, nearly 5k entries) [Select a TV Show] drop-down. On FF (and IE/Edge FWIW) there is a noticeable delay in opening. I'd say 200-400ms. On Chrome it opens instantly.

Next, have something playing that consumes decent amounts of CPU in a tab. I used twitch. Then go somewhere and rapidly open new links (I middle-clicked around on Wikipedia). After about 10 tabs, FF starts slowing down (opening tabs that look like blank tabs and only starting to load after a delay) and possibly interrupts playback in the background tab. IE/Edge are even worse and will start opening tabs slower than you click and keep opening for a while after you are done. In Chrome on the other hand, everything is instant.

I'm on Windows 10 and everything is up to date. I'd love for someone to tell me that it's different for them.

Re:State of web browsers in 2018 by skykooler on Thursday December 06, 2018 @03:50PM (#18622075)
Interesting. I have pretty much the opposite experience on MacOS; with Chrome, if I open a bunch of tabs (~50), my memory usage quickly goes to 15.9 of my 16 GB, and then my whole system slows to a crawl. In Firefox, the same number of tabs are using less than half of that, and everything is still running smoothly.
Re:State of web browsers in 2018 by bzbarsky on Tuesday December 11, 2018 @11:26AM (#18656395)
I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1513256 to track that drop-down issue, which is quite easily reproducible.
Re:State of web browsers in 2018 by simfoo on Tuesday December 11, 2018 @07:13AM (#18654805)
Just did the test with the drop-down menu on Chromium 71.0.3578.80 and Firefox 63.0.3 both running on Ubuntu 18.10. I can confirm the difference in performance, FF takes at least 1s longer to open the menu
Re:State of web browsers in 2018 by seba_dos1 on Tuesday December 11, 2018 @10:37AM (#18655958)
I have 8GB RAM. It doesn't matter to me that Chrome would be faster if it could eat 4 times the whole RAM I have - what matters is that it's not.

Also, it's a pretty weird test case to compare performance, probably not related to anything that actually matters. What's more, Firefox tries to style the drop-down to match with the system UI, while Chrome doesn't even bother.

Re:State of web browsers in 2018 by Semaphor on Tuesday December 11, 2018 @05:12PM (#18659461)
> I have 8GB RAM. It doesn't matter to me that Chrome would be faster if it could eat 4 times the whole RAM I have - what matters is that it's not.

I specifically said that I can see it being a problem in low ram cases.

> Also, it's a pretty weird test case to compare performance, probably not related to anything that actually matters.

This is not some random benchmarks. Both of these problems are things that I regularly encounter on actual websites. And it's great that FF styles it, but I'd rather have performance than system appropriate dropdowns.

Re:State of web browsers in 2018 by seba_dos1 on Wednesday December 12, 2018 @09:52AM (#18664354)
The only reason 8GB RAM can be considered "low" instead of "appropriate for most workloads" is Chrome.
Re:State of web browsers in 2018 by Semaphor on Friday December 14, 2018 @07:20PM (#18686124)
I don't even run Chrome outside of testing compatibility. I do run Visual Studio, often multiple instances. Right now I don't, only FF, a few apps and Stellaris (which only uses around 500 MB), yet I'm still at nearly 16GB of Memory usage. 8GB might be enough for many (most?) people, but not for me, and it has nothing to do with Chrome.
Re:State of web browsers in 2018 by seba_dos1 on Sunday December 16, 2018 @05:29AM (#18692522)
I also sometimes long for more RAM, but those situations definitely aren't what can be sanely considered "most workloads".
Re:State of web browsers in 2018 by CWuestefeld on Thursday December 06, 2018 @12:05PM (#18619791)
Chrome has separate processes for each tab, as well as for each extension. In my Windows install I right now have only 3 tabs open, but it's using 24 processes. And in my experience, those processes all carry a goodly amount of overhead: even a simple page seems to consume 10s of MB, as does even a simple extension with no UI. I just created a HelloWorld page with nothing but that text, and it alone is consuming one process with 22.9MB.

In contrast, Firefox pools those processes. I currently have 56 tabs open, but only 6 Firefox processes running, consuming a total of 1.7GB. So for example, there is (AIUI) just one single process that's responsible for all rendering behavior. I don't have the same detailed information about how much resources that HelloWorld page is taking, but it feels more efficient to me.

Re:State of web browsers in 2018 by detaro on Thursday December 06, 2018 @11:40AM (#18619549)
The Quantum change introduced multi-process to Firefox too. With a proper adblocker, hundreds of tabs are not a problem in my experience ( Chrome needs one too: in hundreds of random pages it's just too likely some crazy ads stress the system by playing video, constantly loading data, ...).
Re:State of web browsers in 2018 by timerol on Thursday December 06, 2018 @12:15PM (#18619918)
Quantum did a bunch to speed up rendering, and Electrolysis added a multi-process architecture that makes more sense than Chrome, IMO. You essentially have a main process and multiple content processes. The number of content processes is limited to some sane amount, instead of 1/tab.
Re:State of web browsers in 2018 by hnaccy on Thursday December 06, 2018 @01:41PM (#18620779)
I have 1450 tabs open and Firefox is fine, Chrome would be an unusable mess.
Re:State of web browsers in 2018 by TMWNN on Tuesday December 11, 2018 @02:06PM (#18657866)
I use ~1200 tabs. I used to deal with Chrome stalling by periodically killing all Google Chrome Helper processes, and a few months ago switched to Firefox (less sluggish) from Chrome. Last week I decided to try Chrome again and was pleased to find that (with the same tab set) Chrome 71 is amazingly fast; new tabs open instantly, I can immediately enter a search query or URL, and the browser remains stable over time. Firefox, by contrast, is noticeably slow (but better than older Chrome) when opening new tabs or handling queries. So it's back to Chrome for me; it is now only slow when starting for the first time, when it processes the 1200 tabs for a few minutes.

(I do use The Great Discarder, but did so before switching to Firefox, too.)

Re:State of web browsers in 2018 by machiaweliczny on Thursday December 06, 2018 @12:56PM (#18620377)
Not true in my experience.

I liked firefox on mobile for ability to use addons. But with some update it started being totally unresponsive and crashing my phone, so I switched back to chrome which happily displays ":)" with 100+ tabs open.

On mac firefox is eating battery faster than chrome.

I would like some alternative for phone - so I will maybe try vivaldi or brave or test firefox once again.

Re:State of web browsers in 2018 by Wowfunhappy on Thursday December 06, 2018 @02:02PM (#18620981)
> On mac firefox is eating battery faster than chrome.

If you're on a Mac and want better battery life when web browsing, Safari will do better than both Firefox and Chrome in most cases.

Re:State of web browsers in 2018 by wyclif on Thursday December 06, 2018 @06:52PM (#18623747)
That's why the only time I ever use Safari on my MBP is when I'm away from a power source. Which isn't very often.
Re:State of web browsers in 2018 by akavel on Thursday December 06, 2018 @11:12AM (#18619237)
Uh, crashing??? I, like, never actually switched to Chrome in the first place (only using it sometimes for sites that "only work in IE^H^HChrome"), am using Firefox on multiple computers on Linux and Windows, and absolutely don't remember it crashing, for years at least!

(edit: tweaked to clarify)

edit 2: using Firefox on mobile (Android) too, for ~2 years now (i.e., since I have a smartphone), cannot recall a single crash over that timeframe either.

Re:State of web browsers in 2018 by SamWhited on Thursday December 06, 2018 @11:19AM (#18619319)
Chrome or Firefox? I meant that Firefox mobile crashes more frequently than the others (in fact, specific sites make it crash consistently and have done for years; I could probably dig some up, but I gave up reporting them since none of the bugs have been fixed for years to my knowledge). For the most part it's still not a frequent occurrence I suppose, but it only has to happen once or twice on a popular website to make someone switch away.
Re:State of web browsers in 2018 by akavel on Thursday December 06, 2018 @11:47AM (#18619629)
Would be curious about the websites indeed!
Re:State of web browsers in 2018 by dbrgn on Thursday December 06, 2018 @04:20PM (#18622346)
Me too. I've been using Firefox for quite a while now (on a Fairphone 2, which is rather slow) and it performs fine and never crashes.

I particularly love the possibility of opening multiple links at once in the background, and buffering them until I switch to the Firefox app.

Re:State of web browsers in 2018 by PurpleRamen on Thursday December 06, 2018 @11:00AM (#18619111)
> The user interface is good, the browser is responsive and reasonably fast.

Ever used chrome or some other browser on android? The droidfox is quite infamous for it's slowness and backward interface.

Re:State of web browsers in 2018 by Yizahi on Thursday December 06, 2018 @11:29AM (#18619424)
I used Chrome and Samsung one and Firefox. There is no perceptible difference in speed of the browser, only in speed of mobile internet. I switched to FF a year ago as a main mobile browser and it works just fine.
Re:State of web browsers in 2018 by StyloBill on Thursday December 06, 2018 @11:39AM (#18619534)
> There is no perceptible difference in speed of the browser

No difference that maybe you can perceive, but I for one find the scrolling a lot more sluggish on FF than on Chrome, and that's on a SD 845 device, which is the latest and supposedly greatest Qualcomm chip. I just can't use FF on Android, and that's a shame because the desktop version is very good.

Re:State of web browsers in 2018 by Spivak on Thursday December 06, 2018 @12:17PM (#18619964)
Tumblr was the site that got me to switch away from Firefox on Android to Brave. Firefox scrolling was like watching a slideshow, the animations would happen 5 or so seconds after you tap but Chrome/Brave was as smooth as the native app.
Re:State of web browsers in 2018 by adimitrov on Thursday December 06, 2018 @04:11PM (#18622282)
Yes. Yes, actually, I have. It's neither slow, nor do I find its interface bad. Actually, I think it's way better than Chrome on Android, because I like the way the new tab functionality works (and I sometimes keep around 20-30 tabs open on mobile.)

My phone isn't even some flagship. It's an OP3T, and it copes very well with FF.

Re:State of web browsers in 2018 by Y_Y on Thursday December 06, 2018 @11:03AM (#18619140)
It also syncs nicely with the desktop version sharing tabs and passwords and whatnot. Even if Chrom* was as good as firefox there, the mobile aspect would make the difference
Re:State of web browsers in 2018 by zeveb on Thursday December 06, 2018 @11:30AM (#18619437)
Sadly, the sync functionality is gated behind an insecure authentication system, so one really shouldn't use it. This is a pity, because Chrome's sync is even less secure.

Compounding the pity, Firefox used to have a more secure auth system, which they threw away. I'm still appalled by that.

Re:State of web browsers in 2018 by Steltek on Thursday December 06, 2018 @12:12PM (#18619875)
While I really liked the old sync system, it was never going to be user-friendly because it entrusted key management/safety to users. People just aren't ready for that and Mozilla maintaining two systems would compound the user issues.

I would accept running my own server for Sync as a solution and I believe this was even possible with the old system? Then power users could have that extra layer of security if they desired but regular users don't have to worry so much.

Re:State of web browsers in 2018 by zeveb on Friday December 07, 2018 @07:31AM (#18627094)
If they would simply get rid of all HTML submissions pages where users may enter their passwords, then the system would probably acceptable. If the Firefox Account UI were entirely browser-managed, it'd be okay. I'd still prefer a system in which it's impossible for users to accidentally leak their secure data through use of a poor password, but that's life.

As an aside, I don't see that user key management was really an issue. The UI of the old system was perfectly fine, and one could have added a QR code or similar if one really wanted to. The number of folks doing TOTP auth these days prove that it works.

There's only one reason to use dynamically-downloaded JavaScript to ensure user privacy: because one wishes to silently and undetectably undermine user privacy at some point in the future.

Re:State of web browsers in 2018 by nmeofthestate on Thursday December 06, 2018 @12:29PM (#18620107)
I have tried using Firefox mobile on Android, but didn't enjoy it - it suffered from sluggish UI interaction. If it was technically on a par with Chrome I would consider going to make the effort to migrate.

Firefox has never been bundled with a mainstream OS, mobile or desktop, as far as I know, it's always been something that people sought out. I think since you can install it on Android, if it's any good it has a chance of success.