Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mozilla Firefox – Official GitHub repo

github.com

Post reply on HN
Print view View original

81–90 of 481 posts

Re: Mozilla Firefox – Official GitHub repo

#81

Post by Kuinox »

swiftcoder wrote: post #15
shit_game wrote: post #4

Earlier quoted context omitted.

firefox development has been moved from mercurial to git since early november of 2023 https://www.phoronix.com/news/Firefox-Going-Git

Interesting that their issues are blamed on "dual SCM", not on Mercurial itself. I guess just the weight of contributors expecting Git as the default is sinking the big Mercurial projects these days.

I tried to contribute a few years ago. The mercurial clone was taking multiple hours. They already had an non official git, which took 15 minutes to clone.

Re: Mozilla Firefox – Official GitHub repo

#82

Post by AStonesThrow »

flohofwoe wrote: post #79
sshine wrote: post #60

Earlier quoted context omitted.

> if github goes down you could still generate patches and email them around, and then push back to github when it's back. You could, but generally people can’t. They learn a set of narrow workflows and never explore beyond. GitHub use translates into GitLab use, but not into general git use workout a central repository. > Everything surrounding code: issues, CICD, etc, is obviously another story. But it's not a stor…

> They learn a set of narrow workflows and never explore beyond. And tbh, that's how it should be for a version control system. Before git with its byzantine workflows and a thousand ways to do the same thing, version control (e.g. svn) was a thing that's just humming along invisibly in the background, something that you never had to 'learn' or even think about, much like the filesystem. I don't need to know how a fi…

https://m.xkcd.com/1597/

Re: Mozilla Firefox – Official GitHub repo

#83

Post by floriangosse »

I think it's actually an understandable strategical move from Mozilla. They might loose some income from Google and probably have to cut the staff. But to keep the development of Firefox running they want to involve more people from the community and GitHub is the tool that brings most visibility on the market right now and is known by many developers. So the hurdle getting involved is much lower.

I think you can dislike the general move to a service like GitHub instead of GitLab (or something else). But I think we all benefit from the fact that Firefox's development continues and that we have a competing engine on the market.

Re: Mozilla Firefox – Official GitHub repo

#85

Post by pndy »

gsich wrote: post #13
reddalo wrote: post #6

Why GitHub? If they truly cared about open-source they would've chosen something else, such as a self-hosted Forgejo [1], or its most common public instance Codeberg [2]. [1] https://forgejo.org/ [2] https://codeberg.org/

Probably only for visibility. Or MS is in the process of sponsoring them.

Considering image backlash they had over last year with: acquiring ad tech company created by former meta people, which in turn lead to introducing so-called "privacy preserving attribution" feature for ads tracking, changing ToS terms regarding data collection, firing CPO who was diagnosed with cancer. Then I do believe these all little changes are PR stunts with an attempt to regain trust of users who strongly criticised Mozilla in last year and earlier.

They should restructure instead, hire people who actually want to work on software and not use corporation and foundation around it as platform for their... peculiar "endeavours". But I doubt that's gonna happen - flow of Google cash and from all those naive people who think supporting Mozilla directly contributes to Firefox is too good it seems. But then it's understandable they do this - money from Google tap can get twisted.

Re: Mozilla Firefox – Official GitHub repo

#86

Post by baq »

groestl wrote: post #50
enos_feedler wrote: post #41

Earlier quoted context omitted.

And how are we suppose to solve this problem? By creating distributed versions of every possible component of every piece of software? Seems unrealistic. I think we should be grateful that the core underlying protocol for the most important data has the distributed properties we want. It's a lot more than we can say vs. lots of other platforms out there.

> And how are we suppose to solve this problem? By creating distributed versions of every possible component of every piece of software? Seems unrealistic. That's how we started out.

Maybe that's the reason everything tends to get centralized.

Re: Mozilla Firefox – Official GitHub repo

#87

Post by baq »

flohofwoe wrote: post #79
sshine wrote: post #60

Earlier quoted context omitted.

> if github goes down you could still generate patches and email them around, and then push back to github when it's back. You could, but generally people can’t. They learn a set of narrow workflows and never explore beyond. GitHub use translates into GitLab use, but not into general git use workout a central repository. > Everything surrounding code: issues, CICD, etc, is obviously another story. But it's not a stor…

> They learn a set of narrow workflows and never explore beyond. And tbh, that's how it should be for a version control system. Before git with its byzantine workflows and a thousand ways to do the same thing, version control (e.g. svn) was a thing that's just humming along invisibly in the background, something that you never had to 'learn' or even think about, much like the filesystem. I don't need to know how a fi…

svn was not 'humming' unless you confined yourself to a very narrow set of functionality, e.g. merging was best left to experts.

Re: Mozilla Firefox – Official GitHub repo

#88

Post by nirava »

calcifer wrote: post #65
rrr_oh_man wrote: post #51

Earlier quoted context omitted.

> If you had checked you would've seen issues are not enabled That was the point of the (obviously ill-received) joke.

Ill-received or poorly stated? Try as I might, I can't find a joke in your comment.

I can. It was funny.

No serious engineer will read that line and think, "wow, how malicious of mozilla, they just made the move to close all bug reports at once".

Re: Mozilla Firefox – Official GitHub repo

#89

Post by eXpl0it3r »

sph wrote: post #73
qwertox wrote: post #63

Earlier quoted context omitted.

In Codeberg, how does one even search for files containing a given string? Probably the #1 thing I do on GitHub is searching for files in a project containing a given string.

Given how terrible GitHub search in files is, what I usually do is clone the repo and run ripgrep.

Not sure when you tried last, but it's gotten a lot better over the years. If you need something from the latest master, you'll be able to find it.

Re: Mozilla Firefox – Official GitHub repo

#90

Post by writebetterc »

flohofwoe wrote: post #79
sshine wrote: post #60

Earlier quoted context omitted.

> if github goes down you could still generate patches and email them around, and then push back to github when it's back. You could, but generally people can’t. They learn a set of narrow workflows and never explore beyond. GitHub use translates into GitLab use, but not into general git use workout a central repository. > Everything surrounding code: issues, CICD, etc, is obviously another story. But it's not a stor…

> They learn a set of narrow workflows and never explore beyond. And tbh, that's how it should be for a version control system. Before git with its byzantine workflows and a thousand ways to do the same thing, version control (e.g. svn) was a thing that's just humming along invisibly in the background, something that you never had to 'learn' or even think about, much like the filesystem. I don't need to know how a fi…

You don't need to learn how git works internally to be able to use it. You need to know a lot about filesystems in order to use them: Folders, files, symbolic links, copy, cut, paste, how folders can exist on different devices, etc. There's just a tonne of assumed knowledge regarding them, and it's very obvious when you meet someone that doesn't have it (regular people often don't have all it).

Subversion also isn't some thing humming along invisibly in the background, it has its own quirks that you need to learn or you'll get stung.

Post reply on HN