You don't see this every day:<p><a href="https://github.com/dspinellis/unix-history-repo/blob/Research-PDP7-Snapshot-Development/lcase.b" rel="nofollow">https://github.com/dspinellis/unix-history-repo/blob/Researc...</a><p>Is this B, or is it BCPL? What would have compiled this code back in the day?
This repo has been super useful as I've been writing a book that teaches Rust by rewriting classic Unix utilities. I settled on using the 4.4 BSD source as a base but having the whole history available has been really interesting. Recently I came across a bug in the 4.4 version of cat that wasn't fixed until a few years later (in FreeBSD).
Gource Visualization video which points to <a href="https://www.youtube.com/watch?v=S7JB0mhrGCQ" rel="nofollow">https://www.youtube.com/watch?v=S7JB0mhrGCQ</a> does not work anymore.<p>> Video unavailable
> This video is no longer available because the YouTube account associated with this video has been terminated.
You don't see this every day.....<p>But you do see it every year for the last number of years<p>Some previous discussion from 3 years ago:<p><a href="https://news.ycombinator.com/item?id=19429249" rel="nofollow">https://news.ycombinator.com/item?id=19429249</a>
We have all this commit data at scale, it really feels like there are interesting stories or lessons that could be extracted from them.<p>There's kind of the obvious operational stuff like: What are the properties of commits that introduce bugs compared to those that don't. Which type of commits are rarely changed and which are more likely to be changed over time. But what I'd find even more interesting is some insight into how we solve problems and how well we're able to solve them. I guess part of the puzzle is missing - the external requirements / environment that give rise to some number of the commits.