SaaSHub helps you find the best software and product alternatives Learn more →
Unix-history-repo Alternatives
Similar projects and alternatives to unix-history-repo
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
src
Read-only git conversion of OpenBSD's official CVS src repository. Pull requests not accepted - send diffs to the tech@ mailing list.
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
freebsd-src
The FreeBSD src tree publish-only repository. Experimenting with 'simple' pull requests....
-
-
-
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.
-
-
intellij-rainbow-brackets
🌈Rainbow Brackets for IntelliJ based IDEs/Android Studio/HUAWEI DevEco Studio/Fleet
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better unix-history-repo alternative or higher similarity.
unix-history-repo reviews and mentions
Posts with mentions or reviews of unix-history-repo.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-17.
-
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.
-
A note from our sponsor - SaaSHub
www.saashub.com | 18 May 2024
Stats
Basic unix-history-repo repo stats
51
6,434
0.0
almost 2 years ago
dspinellis/unix-history-repo is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of unix-history-repo is Assembly.
Popular Comparisons
- unix-history-repo VS PySyft
- unix-history-repo VS rss-proxy
- unix-history-repo VS intellij-rainbow-brackets
- unix-history-repo VS m1n1
- unix-history-repo VS typos
- unix-history-repo VS insect
- unix-history-repo VS Ruby Units
- unix-history-repo VS Gource
- unix-history-repo VS coreutils
- unix-history-repo VS linux
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com