| kcc | pf | |
|---|---|---|
| 1 | 1 | |
| 180 | 7 | |
| 0.0% | - | |
| 10.0 | 4.0 | |
| over 1 year ago | 5 months ago | |
| C | ||
| MIT License | BSD 2-clause "Simplified" 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.
kcc
-
Origins of J
true. only k is faster, easier to learn, and does the trick :)
that said, i hold the view that mastering programming in an ultra-high level language such as APL or k does not absolve a computer programmer from learning lingua franca of our trade, which is due to k&r, will stay around for a very long time, and is called C.
people who don’t know c are ok, only they are not involved in computer programming. their field is known as software development. feel the difference.
i once attempted to convey my own understanding of this divide in a chapter titled “no stinking loops”, which is a nod to Apter’s mandatory nsl.com:
https://github.com/kparc/kcc#no-stinking-loops
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
What are some alternatives?
ooj - the origins of J