Hacker News new | ask | show | jobs
by lucasyvas 1737 days ago
It's beyond me why they haven't thrown it up on GitHub yet. Let the community have a way bigger involvement and drive the future of the browser. Yes, I can go find the source for Firefox, but I sincerely doubt the engagement is anywhere near as high as it could be.
2 comments
shp0ngle 1737 days ago
I’m not sure accessibility of source code is the biggest problem. You can get the code very easily. Also github is another kind of Microsoft lock-in, ironically.
link
lucasyvas 1737 days ago
I don't necessarily disagree with your Microsoft comment. I'm merely trying to say that I think Firefox needs more than features to reclaim some of its popularity.

Where we're at, is that most people are happy running a Chromium variant. It's open source and there are enough downstream consumers that you can pick your poison.

If Mozilla is going to push the "private browser, for you" angle, they are going to need to push harder on the "for you" angle.

I'm still a loyal Firefox user. It seems to me that its users would rather have more say in its direction - give the people what they want.

link
toastal 1736 days ago
If you don't disagree with the monopoly statement, then start altering your speech to reflect it. You can use the phrase “(public) Git forge” and avoid using the trademark generically and encompass all alternative forges.
link
lucasyvas 1736 days ago
In this case, I think that the leading Git provider is where it should be hosted, due to community size. And that's GitHub for now. That can absolutely change in the future.
link
toastal 1736 days ago
Git was created to be distributed. Endorsing an account-required, closed-source platform is not the best play for Git as platform (nothing wrong with it having accounts, and the account providing an improved experience). IMO, it is important regardless of what platform's in vogue to use a more generic term here.
link
iggldiggl 1735 days ago
One doesn't follow from the other. Firefox for Android is now on Github, but at the same time we've still ended up with about:config locked down in Release, add-on support locked down in Release, ... because it's still very much Mozilla setting development policy.
link