unix-history-repo
langs
unix-history-repo | langs | |
---|---|---|
51 | 185 | |
6,434 | 86 | |
- | - | |
0.0 | 9.3 | |
almost 2 years ago | 4 days ago | |
Assembly | C | |
GNU General Public License v3.0 or later | - |
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.
langs
- How does the compiler know that an already typedefed ident is meant to be a new declarator?
- Compiler Case Study
- Making Simple Concepts Hard
- What makes a language easy for writing a parser?
-
Resources to understand mojo and compilers
The code is here. Note that the input filename is hardcoded in the source code.
- Automatic import of C headers —how to deal with macros?
- How does preprocessing work in a one pass compiler?
- 'Table Data' and 'X-Macros'
- Register Window in a Stack VM Interpreter
- My New IL
What are some alternatives?
PySyft - Perform data science on data that remains in someone else's server
prolog-to-minizinc - A Prolog-to-MiniZinc translator
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.
rakudo - 🦋 Rakudo – Raku on MoarVM, JVM, and JS
intellij-rainbow-brackets - 🌈Rainbow Brackets for IntelliJ based IDEs/Android Studio/HUAWEI DevEco Studio/Fleet
vox - Vox language compiler. AOT / JIT / Linker. Zero dependencies
m1n1 - A bootloader and experimentation playground for Apple Silicon
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
typos - Source code spell checker
wabt - The WebAssembly Binary Toolkit
insect - High precision scientific calculator with support for physical units
factor - Factor programming language