Hacker News new | ask | show | jobs
by tucnak 564 days ago
It's many things; overall low-quality compared to Chromium. Thankfully they have deprecated XUL a few years back which was really holding people back in major ways, but yeah, it's not good. People don't like to hear that, but that's probably the reason why Chromium won. Much easier to patch it, & the inner layout of components, separation make more sense.
1 comments

Sorry, could you be a bit more specific? As a user, not a developer, I'm curious if there's any flaws in the source code (potential security vulnerabilities, inefficient code that might cause slow / slower execution, dodgy third party data extraction, stuff like that.) that might affect day-to-day user experience. Personally, when I switched from Chrome to Firefox, I found I had much more control over each aspect of the browser experience and that's been the main reason I've stayed. I especially like the "about:config" page, chrome is sorely missing something similar.
Until recently, Firefox was quite slow but with the Quantum release they addressed it somewhat. From a user perspective, I say, if you like it, trust Mozilla, don't care about what they have become, you're fine. In my opinion, it's only downhill from here. That said, I think they did a good job over the years on security, the containers are neat, however the profile design in Chromium is probably superior. The majority of Web security research comes from Google, they invest deeply into security, although it doesn't matter as much because they're also cooperating with the industry, coordinated release is a thing, etc. The cache model specifically is more powerful in Chromium; memory usage is often touted as advantage for Firefox, but it's a statement on how Chromium cache model is superior more than anything.

I'm not sure what "aspects of the browser experience" you're referring to specifically, but I would guess it's probably marginal as in terms of Web standards Firefox is playing catch-up. It took them a long time to implement JIT in the engine at the point when V8 had it for years; touted as a huge accomplishment, and it was—considering how it's so hard to work with Firefox codebase. There's a dedicated group of developers punching above their weight, unfortunately they're at a disadvantage.

Hmm... alright, thank you. I'll stick with what I've got for now. You're right though, it seems like Mozilla is looking for a way to monetise their platform, at the expense of user experience.

You mentioning memory usage reminds me of this article, which was actually the reason I switched over. [https://www.pcmag.com/news/firefox-power-user-keeps-7400-plu...] Not sure if you could do that in Chrome!