Hacker News Reader

Comment by Rolcol | Hacker News Reader

You claim it's dead, but suggest using a fork that can't hope to keep up if Firefox dies? They benefit from all the architectural improvements done to Firefox, including this.

View on HN

You don't have a high opinion of the LibreWolf team.

Did you know that I can still use a web browser from the last decade to surf websites? Yup.

Even if FF dies, the codebase is opensource and continue to be developed.

The repo's members page [0] shows 9 users, and the first bullet point on its features page [1] is: LibreWolf is compiled directly from the latest build of Firefox Stable. You will have the the latest features, and security updates.. You believe a small group of well-intentioned volunteers can continue the work of building and iterating a modern web browser were Firefox development to end today?

[0] https://gitlab.com/groups/librewolf-community/browser/-/grou...

[1] https://librewolf-community.gitlab.io/docs/

It's possible, maybe not very likely but possible. Depends what happens to FF.

No, it's not. Mozilla has 750 employees (not all of whom work on the browser, but still) and hundreds of millions of dollars and they're constantly struggling to keep up with Chrome. 9 part-time devs cannot do this.

They can. Maybe releases would be every 6 months but it's possible.

Look at the following browsers: Otter Browser Min Qutebrowser Links Basalisk Surf Bromite (only has 7 contributers)

It is possible. Of course it's possible. Just depends if that situation were ever to occur, whether people would become passionate about that project

We're talking about different things. I'm sure the LibreWolf team could develop a browser that meets some specifications and renders some websites some of the time. What they can't build is a Chrome competitor. It would become an often-broken hobby project only used by enthusiasts, like the others you've listed.

Otter and qutebrowser are based on QtWebEngine which is a wrapper around Blink (Chromium's engine), Min is using Electron which is also a wrapper around Blink, surf uses WebKitGTK which is a wrapper around WebKit (Safari's engine) and Bromite actually says is a Chromium's fork. The contributors for those browsers have to only maintain the GUI which is just the tip of the iceberg. As for Links, it cannot render most of the web.

Basilisk and its sibling Pale Moon are an example of how hard a fork is (both being pre-Quantum Firefox); features removed because cannot be maintained, incompatibilities, poor performance and many vulnerabilities.

thanks for that info

Reply on news.ycombinator.com