eo
jcabi-github
eo | jcabi-github | |
---|---|---|
4 | 2 | |
907 | 302 | |
2.4% | 0.7% | |
9.9 | 8.4 | |
6 days ago | 7 days ago | |
Java | Java | |
MIT License | 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.
eo
-
The Code and Its Tests in Different Pull Requests
Looking at the commit history of eo, I'm not certain that PR size, or testing methodology for that matter, should be the #1 concern of Yegor's team.
- EO - object-oriented programming language based on 𝜑-calculus
-
Eolang, an Experimental Object-Oriented Programming Language Based on 𝜑-Calculus
They do have a paper in the repo: https://github.com/cqfn/eo/tree/master/paper
According to it, "𝜑-calculus" is something they made up for the eolang and not a standard term.
Here is my take on that calculus based on reading through section 3 in the paper. Note the paper is pretty weird and likes to make its own notation, so it is possible I got some things wrong:
It is starts with a pretty standard immutable language: "object" is a set of (name, value) pairs; "value" is either object or "data" (like a string, bool etc...); everything is immutable but you can make a copy an object with some attributes changed. There are no concept of "types" -- instead, you define objects with some fields set to NULL (spelled ∅ in the paper). There are also a bunch of term defined, like "abstraction", "application", etc.. -- but they all mean "make a copy of an object with some fields changed".
The "twist" is that the language has no functions per se, instead it defines AST-like structure: there is a syntactic sugar that handles things that look like function applications. So when you see:
stdout "Hello world"
jcabi-github
-
Commit-teller - Problems during the development
The jcabi-github dependency looked nice in the beginning but it was having issues with the event feed management, the endpoints were not properly setup in the code, but it was only a minor issue, I was able to overcome it by using two different operations to fetch the required data.
-
I made a java client for the todoist api
Here's an example of what I mean: https://github.com/jcabi/jcabi-github/ (it's a Java client for Github's API).
What are some alternatives?
AnySoftKeyboard - Android (f/w 2.1+) on screen keyboard for multiple languages.
RagTag
golo-lang - Golo - a lightweight dynamic language for the JVM.
quarkus-github-api - Quarkus extension for the Hub4j GitHub API
awesome-wasm-langs - 😎 A curated list of languages that compile directly to or have their VMs in WebAssembly
RagTag
jpeek - Hosted and command-line calculator of cohesion metrics for Java code
github-api - Java API for GitHub
edina - Edina - A simple stack-oriented compiled programming language.
openai-java - OpenAI Api Client in Java
github-plugin - Jenkins GitHub plugin