Re:Firefox Development Is Moving from Mercurial to Git
by fhd2 on Monday November 06, 2023 @05:42AM
(#38160925)
I never understood how people can happily figure out a gigantic, complicated code base like Firefox and are taken aback by learning a little bit about some tool. In your case, was it a thing where working with an unfamiliar tool was simply demotivating? Cause I think if you can write a Firefox patch, you should be able to learn Mercurial during breakfast.
[ Parent
| on HN ]
Re:Firefox Development Is Moving from Mercurial to Git
by bdd8f1df777b on Monday November 06, 2023 @06:03AM
(#38161046)
I could resonate with him/her if I were not familiar with Mercurial. Because he/she is aiming to fix or improve Firefox, figuring out a gigantic, complicated code base of Firefox is directly towards his/her end goal. Meanwhile, figuring out hg feels a waste of time.
Re:Firefox Development Is Moving from Mercurial to Git
by 4death4 on Monday November 06, 2023 @06:32AM
(#38161209)
Is not wanting to do extra work really that hard to understand?
Re:Firefox Development Is Moving from Mercurial to Git
by madeofpalk on Monday November 06, 2023 @07:55AM
(#38161942)
I didn't need to figure out a gigantic, complicated codebase. I only needed to figure out devtools frontend which is a significantly smaller portion of it and relatively self-contained.
Re:Firefox Development Is Moving from Mercurial to Git
by PH95VuimJjqBqy on Monday November 06, 2023 @01:11PM
(#38166307)
For the same reason I get frustrated when I go to solve problem A, run into problem B then while trying to solve problem B I run into problem C. Soon enough you have 15 problems you want solved but you find yourself having to unwind a stack 1 by 1 until you _finally_ get to a point where you can actually solve the original problem.
People probably view dealing with the FF codebase as part of Problem A, dealing with mercurial is Problem B, which is must less appreciated.