emacs-release
A history of Emacs releases, under version control (by jwiegley)
crapbenchmarks
By Nomarian
emacs-release | crapbenchmarks | |
---|---|---|
1 | 1 | |
36 | 0 | |
- | - | |
10.0 | 10.0 | |
over 4 years ago | over 1 year ago | |
Emacs Lisp | Roff | |
GNU General Public License v3.0 only | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
emacs-release
Posts with mentions or reviews of emacs-release.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-24.
-
Want cleaner code? Use the rule of six
At least for the contrived example from the article, the solution isn't to break up the code, but to use denser code. Use a regex.
Does anybody really think that e.g. sregex[1] is better than just learning and using the regex language directly? Because that's where this kind of thinking leads.
[1]: https://github.com/jwiegley/emacs-release/blob/master/lisp/o...
crapbenchmarks
Posts with mentions or reviews of crapbenchmarks.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-24.
-
Want cleaner code? Use the rule of six
Beat me to it. Yes, I ran a quick benchmark[0] and not running a function always wins. now, one may argue that you are running a call, but if the interpreter was smart it would convert the small function calls to just a noops.
[0]: https://github.com/Nomarian/crapbenchmarks/tree/main/call
Summary
What are some alternatives?
When comparing emacs-release and crapbenchmarks you can also consider the following projects:
jsource - J engine source mirror
kdb - Companion files to kdb+ and q
hebigo - 蛇語(HEH-bee-go): An indentation-based skin for Hissp.