Live data from Hacker News

A look at Firefox forks

lwn.net

221–230 of 390 posts

Re: A look at Firefox forks

#221
post #8

I read in a few places that LibreWolf's anti-fingerprinting features are breaking websites. One person complained that their meeting got scheduled incorrectly because the browser was messing with the user's time zone (for privacy reasons).

It uses UTC, as everyone should.

Re: A look at Firefox forks

#222
post #110

Are the rhel RPM distributions of Firefox considered forks at all? They are maintained for a very long time.

IIRC Red Hat now just ships the Firefox ESRs and does not support a single version for the entire life of a RHEL release. You probably wouldn’t want a 10-year old browser anyway. And, in RHEL 10, they have stopped packaging Firefox in favor of a Flatpak.

Re: A look at Firefox forks

#223
post #205

Earlier quoted context omitted.

I am a bit confused by their moving from C++ to Swift instead of Rust. It sounds a bit Apple-first. I get that it ports to Linux okay, but will it be hard to make it work with Windows some day?

Rust makes more sense if you were to start from scratch, but the Ladybird devs said that their code is already heavily OOP, so it maps to Swift a lot better. Also, variety is good, we have Servo in Rust (although I wish they'd make an actual browser around it too).

Yeah I guess it's the same story as with the TSC port to Go

Re: A look at Firefox forks

#226
post #203

In Firefox, you can choose a local html file as your home page, but not as a new tab page. This is allegedly because of some security concerns. Using extentions allows for a limited workaround where the page needs to be re-imported each time it is edited. The surprising part to me is that the same applies to the forks too. If opening a local file for the home page not a security concern, why should it be for the new…

These restrictions are super-annoying indeed, especially with no way to override them. Example: I like mouse gestures. People say oh yes, you can have mouse gestures in Firefox, here, there are several extensions. Well, open a new tab with a mouse gesture. Cool. Now try close it. Same goes for any other "special" page.

Re: A look at Firefox forks

#227
post #119

Earlier quoted context omitted.

Why did Google in 2008 chose to built its own browser instead of helping to improve Firefox, which was around since 2002?

They wanted a browser they have full control over. And you can move much faster when you don’t have to negotiate every change with third parties. Also, Firefox 1.0 and Chrome 1.0 were released within months of each other (though Firefox 0.x had existed for a little while), so Firefox wasn’t that established yet. The main competition at the time was Microsoft Internet Explorer with over 90% market share.

Firefox 1.0: 2004 Chrome 1.0: 2008

Re: A look at Firefox forks

#228
post #78

Earlier quoted context omitted.

If someone was building "Arc but for Firefox" I'd gladly pay for that. Firefox is, because of its position in the market, incapable of doing anything broadly interesting that's not "Be as Chrome-like as possible." They sneak in features that are nice, but I simply don't think we'll ever see Mozilla put out something that does anything that really sets Firefox apart. We'll only ever just get marginally better privacy…

Zen browser is exactly this. It has a growing ecosystem of “Zen mods” and has a great Arc-like out-of-box experience. https://zen-browser.app/

After a short time with it, I find it kinda funny. Back then, power users were up in arms about things like the omnibar, and chrome removing more and more parts of the actual URL. And here is a browser marketed at power users that goes beyond that, showing only a small fraction. There doesn’t even seem to be a Zen mod that restores a real usable URL bar.

For me, I manipulate URLs every day, both for work and private usage. Zen disqualified itself for my type of power usage very quickly, giving me a feeling of being on a small mobile device instead of a desktop PC.

Re: A look at Firefox forks

#229

Earlier quoted context omitted.

You are free to enable WebGl in the settings and install a Plugin that allows for blocking/allowing WebGl. The default should be privacy if you install a browser that focuses on privacy.

Would you expect a "privacy focused" browser to offer you networking disabled by default but the ability to enable completely unrestricted networking in the settings (you can install a plugin for CORS and the like if you want) or to natively provide the privacy controls you need to actually use the browser? If the latter, why is it different depending which attack surface you ask about? If the former, why not just ma…

I have left WebGl disabled and do not miss anything so far (maybe in the future?). Just not my use case.

Network disabled is a straw man argument.

If somebody already has made the effort of creating an extension and maintaining it, why not use that?

Post reply on HN