| pf | altc | |
|---|---|---|
| 1 | 2 | |
| 7 | 13 | |
| - | - | |
| 4.0 | 10.0 | |
| 5 months ago | about 5 years ago | |
| C | C | |
| BSD 2-clause "Simplified" License | MIT License |
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.
pf
-
Origins of J
> soon to be lost to obscurity
well, about that i’m just not so sure.
as we like to say, “skill”, for whatever reason you chose to use quotes, cannot be easily bought on a Turkish fish market.
there are people out there who write atwc, and they are not atw. the following 40 lines of c are written strictly arthur-style, and are occasionally very useful. in the faq section of the readme there is an answer to a popular question “why is it written this way, and how to learn to write software this way”.
https://github.com/kparc/pf
altc
-
Origins of J
> README
good idea, why not
for a more throw-me-in-the-water introduction, here are my notes on another famous public domain release from atw. some remarks are specific to the codebase, but essentially it is a general introduction to atwc:
https://github.com/kparc/bcc/blob/master/d/sidenotes.md
and here’s a less involved way to get lit:
https://github.com/aaalt/altc
What are some alternatives?
j-incunabulum