unix-history-repo
Gource
Our great sponsors
unix-history-repo | Gource | |
---|---|---|
51 | 81 | |
6,434 | 11,119 | |
- | - | |
0.0 | 0.0 | |
almost 2 years ago | 5 days ago | |
Assembly | C++ | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unix-history-repo
-
F/OSS Comics: 8. The Origins of Unix and the C Language
There is also https://github.com/dspinellis/unix-history-repo (Continuous Unix commit history from 1970 until today)
-
Kernighan and Pike were right: Do one thing, and do it well
FWIW, ls in Research-V6 back in 1975 had 10 options. https://github.com/dspinellis/unix-history-repo/blob/Researc...
By BSD 3 in 1980 it had 11 options. https://github.com/dspinellis/unix-history-repo/blob/BSD-3-S...
The thing is, we can see even from the 1970s 'ls' how the Unix model doesn't meet the goal "to chain these simple programs together to create complex behaviors".
There is no option to escape or NUL terminate a filename, making it possible to construct a filename containing a newline which makes the output look like two file entries.
The option for that was added later.
There's also the issue that embedded terminal codes will be interpreted by the terminal.
-
The original source code of the vi text editor, taken from System V
This is what it looked like about 7-8 years earlier: https://github.com/dspinellis/unix-history-repo/blob/BSD-1/e...
- Continuous Unix commit history from 1970 until today
-
50 Years in Filesystems: 1974
RA92 (1989): 16 ms / 8.3 ms.
Note that the RL02 (and V7) and RA92 mentioned in the article are separated by about a decade.
[1] https://github.com/dspinellis/unix-history-repo/blob/Researc...
-
Unix: An Oral History
The earliest version I could find [1] is already written in C.
[1] https://github.com/dspinellis/unix-history-repo/blob/Researc...
-
Linux is not as smooth as windows
Here's a 1997 citation for "top cpu processes." It's not as close to the original 1984 release as I would like, but it's better than Wikipedia. https://github.com/dspinellis/unix-history-repo/commit/aee34003d7964653c44c31f5bf6bcf136b32c4f3
- GitHub was Founded in 2008 But...
-
GPT based tool that writes the commit message for you
> The “why” goes into the PR and more importantly, engineering documentation and inline comments
This just ensures that the “why” is lost when someone comes looking years later.
From experience, SCM metadata is far more durable than just about any other work product we produce. Five decades later and RCS commit info was still available for the Unix sources, and history could be reconstructed: https://github.com/dspinellis/unix-history-repo
I’ve used 35-year-old commit messages to help understand a long-standing issue, decades after all other related organization tooling and data had disappeared.
-
What should be included in a history of the Rust language?
P.S. I remember I looked into early versions of C (they survived in Unix historic releases) and that, finally, revealed to me why C does something really stupid and conflates arrays and slices (pointers). Initially C had no arrays! Or, rather, what it called arrays were, actually, pointers. “Normal” arrays were added at some point, but because these weird slices/pointers were already there that caused endless confusion. It wasn't resolved before C became popular and after that it was too late. Go repeated that mistake with slices, of course.
Gource
- 📓 Versionner et builder l'eBook de son Entretien Annuel d'Evaluation sur Git(Hub)
-
Animating Source Code Evolution
The underlying technology, https://gource.io/, has probably been mentioned here before, but it's a superb tool which produces beautiful animations, so deserves another airing.
-
Show HN: Visualize the Entropy of a Codebase with a 3D Force-Directed Graph
This is really cool. And as OP pointed out, I really like the pipeline integration. Like when linting catches function-level complexity, but in a cross functional way. I prefer to think of programs in layers where the top layers can import lower layers, but never the other way (and also very cautious on horizontal imports). Something like this would help track that.
From the visualization perspective, it reminds me a lot of Gource. Gource is a cool visualization showing contributions to a repo. You see individual contributors buzzing around updating files on per-commit and per-merge.
https://github.com/acaudwell/Gource
- Gource: Software Version Control Visualization
-
Preporuka alata za vizuelizaciju koda
Nešto kao gource?
-
Show HN: Hackreels – Animate your code in HD
Yeah, I was completely distracted trying to figure out what `import { Button, icons } from "ui"` was derived from. Looks like `
That being said, I do like the overall idea of animating code changes. Calls back to that old Facebook sketching app[0] that would let us share replays, and I am a fan of the stories that Gource[1] can tell.Ultimately, though, the sequential text file is a bad metaphor for code. Best thing for it is to split your modules across files.
0. Can't remember the name of it, but something similar is https://sketchtoy.com/
1. https://gource.io/
-
[Asking for feedback] News visualization idea
If the goal is to create a fun animation, then have a look at https://gource.io/ for inspiration.
-
The SQLite Project visualized with Gource
From https://github.com/acaudwell/Gource
-
I see a lot of screenshots of "horribly complex git repos" with like 5 branches that are mildly confusing to follow in this subreddit... I feel like I'm obligated to share this. As part of my job I am personally responsible for managing releases in this repository. (Yes, this is real.)
I wonder what your history would look like in Gource: https://gource.io/
- Gource – Animate your Git history
What are some alternatives?
PySyft - Perform data science on data that remains in someone else's server
Sourcetrail - Sourcetrail - free and open-source interactive source explorer
rss-proxy - RSS-proxy allows you to do create an RSS or ATOM feed of almost any website, just by analyzing just the static HTML structure.
metrics - 📊 An infographics generator with 30+ plugins and 300+ options to display stats about your GitHub account and render them as SVG, Markdown, PDF or JSON!
intellij-rainbow-brackets - 🌈Rainbow Brackets for IntelliJ based IDEs/Android Studio/HUAWEI DevEco Studio/Fleet
vircadia-native-core - Vircadia open source agent-based metaverse ecosystem.
m1n1 - A bootloader and experimentation playground for Apple Silicon
ccache - ccache – a fast compiler cache
typos - Source code spell checker
git-of-theseus - Analyze how a Git repo grows over time
insect - High precision scientific calculator with support for physical units
linux - Linux kernel source tree