Live data from Hacker News

"No, we are absolutely not prepared to [fork Firefox]"

codeberg.org

1–10 of 15 posts

Re: "No, we are absolutely not prepared to [fork Firefox]"

#5
For others who saw this with no context and don't want to read the thread, this is a response from the librewolf team regarding requests made in response to changes to Fireox's terms of service[0], from those who are worried that Mozilla/FF will use this as the first step to selling out.

[0]https://blog.mozilla.org/en/products/firefox/firefox-news/fi...

Re: "No, we are absolutely not prepared to [fork Firefox]"

#7
post #4

Dumb question but why /do/ browsers move quick? Surely we are nearing feature complete. Is it just the complexity of the task? I'm sure there are lots of awful bugs.

Because the scope keeps growing as well. People have been pushing desktop apps to the browser for years.

I wish the browser was limited to showing websites, and that technology for desktop apps evolved. But that's not how it goes for some reason. Some kind of imperialism in platforms? Systemd wants to take it all, browsers want to take it all, ...

Re: "No, we are absolutely not prepared to [fork Firefox]"

#8
post #4

Dumb question but why /do/ browsers move quick? Surely we are nearing feature complete. Is it just the complexity of the task? I'm sure there are lots of awful bugs.

Web standards are moving fairly fast, and modern browsers are getting more and more complex in the process. It would likely be extremely hard, if not outright impossible, to build a browser completely from scratch today because of the sheer amount of moving parts.

Re: "No, we are absolutely not prepared to [fork Firefox]"

#9
post #4

Dumb question but why /do/ browsers move quick? Surely we are nearing feature complete. Is it just the complexity of the task? I'm sure there are lots of awful bugs.

It's simple - interfere with the competition, useless engineer job security, performative "working" , and bad incentives all around. They're on a gravy train and don't want the ad revenue to ever stop. A truly independent browser threatens that entire ecosystem, and that in turn results in collusion and patterns of behavior intended to make things nearly impossible to keep up with, even though the actually functional bits that consumers give a shit about haven't really changed all that much in the last decade. What Microsoft did with IE, all the major browser developers are doing now to reinforce their anti-competitive collective behavior and each can seek as much rent as possible from their respective walled gardens.

Re: "No, we are absolutely not prepared to [fork Firefox]"

#10
post #4

Dumb question but why /do/ browsers move quick? Surely we are nearing feature complete. Is it just the complexity of the task? I'm sure there are lots of awful bugs.

The short response would be the "web browser" started to fill the role of "cross platform on demand app sandbox" instead of "plain hypertext document viewer" and that will forever be evolving to match the capabilities of devices themselves. More than any other contributing reason to the churn (including the highly charged/passionate reasons), if you defined a "web browser" to be a limited subset of the functionality the user desire for a constantly evolving then an "on demand app sandbox" app with a different name would still exist and it'd just be everyone using that application instead of a web browser.
Post reply on HN