The next time you hear someone make an argument against remote work, remind them of what has been achieved in the last 30 years by the Linux kernel developers working across so many different countries and time zones.
The world is so much better off with Linux and Linus and his merry band of hackers. They do an amazing job keeping up with the sheer amount of work that goes into the kernel from everyday needs like you and me to patch sets from companies. But what I am most proud of is git. It’s not perfect but since learning its warts it’s the Swiss Army knife of awesome just like GNU find is for me on the terminal.
Which files get the most commits?<p>Which sections of each files get more than usual commits? eg which functions?<p>Who wrote this particular function first? who subsequently?<p>How many of those include expletives? Curious minds need to know.<p>If I want to answer these earth shattering questions, could I just grab the entire git repo and go from there? is it that simple? is it text exportable without too much "other" scary?
This really speaks to the reliability of Git.<p>Are there any examples of projects with 1kk+ commits that use SVN, Mercurial, Perforce, or some other SCM?
Lot of people view 1mm as a huge number of commits. Which maybe it is... if your team has a habit of big PRs + rebasing.<p>On the other hand, if your team is used to making quick iterative commits, throwing them in a PR, never rebasing, and pulling in merge commits all over the place, uh, I can attest that you can get to a million commits pretty fast.
How do other open source projects compare? I'll admit, I would have figured that Linux had passed one million commits some time ago, and I feel like web browsers might give Linux a run for its money here.
It truly is the greatest open source project of all time. I just wish they moved away from email as the only way of contributing. It doesn't really scale well and definitely doesn't make contributing for newbies easier.
Part of me wonders why nobody tries to make software like we make buildings... After some time, it's all done and nothing else needs to be added.<p>People will be quick to point out that "the hardware keeps changing so the software has to adapt".
This is true, but why not design the software in such a way that different drivers can easily be substituted (so the drivers can change but the interface doesn't)?<p>I did this with my open source project. I haven't made any code changes for over a year and it still works perfectly and still relevant.<p>I don't understand why there is such a fetish in this industry for never finishing any project. I find the whole attitude very frustrating.