Live data from Hacker News

How Firefox Got Fast Again

hacks.mozilla.org

91–100 of 713 posts

Re: How Firefox Got Fast Again

#91
post #52

I switched back to Firefox 54 from Chrome when multiprocess browsing ("Electrolysis") came out of beta. It's been absolutely great. It's fast and I trust and like the nonprofit behind it. And all the extensions I care about are available. My main issue with Chrome was the endless nags to sign in to a Google account, and just generally wanting less dependence on Google. I also like that Firefox has a built in tracking…

https://github.com/Eloston/ungoogled-chromium removes many of the nagging and background features related to Google services.

Re: How Firefox Got Fast Again

#92
post #81

One thing that troubles me is why does a non profit open source browser buy premium offline ad space to promote itself? There's a huge "The new Firefox" ad in down-town Berlin.

Mozilla makes money from having users — it may be open-source but the developers still need to be paid. They don't have a captive audience like Windows or Google.com users to advertise on, so public ads seem necessary.

"Mozilla makes money from having users"

Wait, how does that work again? Last I checked you couldn't deposit users at the bank or pay your rent with them.

Re: How Firefox Got Fast Again

#93
post #5

I have been using 57 in beta, and I have to say, I'm impressed. It is a huge improvement. Whether it keeps me off Chrome in the future remains to be seen though!

Why shouldn't it keep you away from Chrome ? It's faster, uses less memory, and the "maker", Mozilla is more trustworthy compared with Google. What's missing ?

Google Hangouts :-/

Re: How Firefox Got Fast Again

#94

Earlier quoted context omitted.

I have been thinking of switching back from Chrome to Firefox. I haven't been able to find decent profile support though (so I can keep work and private data separate), and all profiles addons are broken at the moment.

firefox -p launches firefox into the profile manager. firefox -p work -new-instance launches your work profile. What are you missing? More options: https://developer.mozilla.org/en-US/docs/Mozilla/Command_Lin...

Thanks, this seems to work. I found the no-remote option when looking around, but accidentally lauching private_dot_com (nsfw) a couple of times at work instead of my private profile ended my testing with this last time.

Re: How Firefox Got Fast Again

#95
I'm still worried about how secure Firefox is in relation to Chrome. From what I understand, Firefox exploits only go for $30k at Pwn2Own, while Chrome exploits go for $80k. Should I be worried?

Re: How Firefox Got Fast Again

#96
post #33

Earlier quoted context omitted.

Same on Windows, I wish the light theme was the default.

I think light is the default for the release version, but devs seem to like dark UIs for some reason.

The reason is eye strain in poorly lit offices :)

Re: How Firefox Got Fast Again

#97
post #85

At a high level my main question is: Why has Mozilla generally been so slow to react to market trends and taken so insanely long to deliver products that are competitive in other ways than fuzzy aspects like openness, freedom etc? This goes back back all the way to like 1998. My memory is a bit fuzzy, but I remember it feeling like they were in rebuilding mode until like 2005-2006. And then Chrome launched in 2008...…

I think Mozilla wasted some effort on some questionable initiatives, like Firefox OS. They became a little complacent and didn't put money(?) where their mouth is. https://en.wikipedia.org/wiki/List_of_Mozilla_products In particular, check out the list of their abandoned projects. But some experimentation is necessary. You're never completely sure when you strike gold.

Maybe the complacency came from having too much money from the first rounds of Google search deals in like 2004-2008?

They had already fulfilled their primary goals (openness, transparency etc.)...

I worked at Opera Software between 2004-2015. We also got loads of Google search placement money in that period, but for all of their other faults, our exec team(s) were able to keep us hungry for more.

Re: How Firefox Got Fast Again

#98
post #81

Earlier quoted context omitted.

Mozilla makes money from having users — it may be open-source but the developers still need to be paid. They don't have a captive audience like Windows or Google.com users to advertise on, so public ads seem necessary.

"Mozilla makes money from having users" Wait, how does that work again? Last I checked you couldn't deposit users at the bank or pay your rent with them.

When a user searches Google from the Firefox toolbar (or Yahoo, or Bing) the relevant search engine pays them a little bit of money.

Re: How Firefox Got Fast Again

#99
post #65
post #5

Earlier quoted context omitted.

Why shouldn't it keep you away from Chrome ? It's faster, uses less memory, and the "maker", Mozilla is more trustworthy compared with Google. What's missing ?

So far, Chrome has better sandboxing support on most platforms (especially Linux), though Chrome's catching up quickly. I'm generally optimistic about Rust code having fewer exploitable defects, although it's a reasonable argument to suggest that the previous C++ parts had a lot more public scrutiny. Also, for me personally: I use a lot of different profiles and using multiple Firefox profiles simultaneously is a mes…

Is https://addons.mozilla.org/en-US/firefox/addon/multi-account... really broken? That was a test pilot experiment till two month ago, it would be very bad (and a bit ridiculous) if that addon were already broken.

Re: How Firefox Got Fast Again

#100
Somewhat tangentially, I really like the cartoons Lin has made. I’ve found I’ve naturally anthropomorphized code. Often when I start working with someone new they get confused when I start talking about constructs like people. I think it’s given me a different perspective on encapsulation and concurrency than most people.

I don’t know if I’ve ever worked with someone that thinks the same way. When I work on code that wasn’t designed that way I force my brain to think like the CPU instead of in terms of little elves with different job... Not sure if anyone else has experienced this 2 modes of thinking about code. It seems like FF engineer’s might be thinking in the same terms as they tackle concurrency refactors.

Post reply on HN