|almost 7 years ago
|about 5 years ago
|BSD 3-clause "New" or "Revised" License
|GNU General Public License v2.0 only
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.
We haven't tracked posts mentioning ascii-art-to-unicode yet.
Tracking mentions began in Dec 2020.
The TypeScript Experience
3 projects | dev.to | 10 Apr 2022
Features of a dream programming language: 2nd draft.
16 projects | dev.to | 10 Feb 2022
Very constrained. Since "constraints liberate, liberties constrain", as Bjarnason said. Inspired by Golang's minimalism, and Elm's guardrails. For learnability and maintainability. Since discipline doesn't scale (obligatory xkcd: with too much power, and the wrong nudges, all it takes is a moment of laziness/crunch-time to corrupt a strong foundation), and a complex language affords nerd-sniping kinds of puzzles, and bikeshedding and idiomatic analysis-paralysis. Counter-inspired by Haskell. The virtue of functional programming is that it subtracts features that are too-powerful/footguns (compared to OOP), namely: mutation & side-effects. The language designers should take care of and standardize all the idiomacy (natural modes of expression in the language). "Inside every big ugly language there is a small beautiful language trying to come out." -- sinelaw. The language should assume the developer is an unexperienced, lazy, (immediately) forgetful, and habitual creature. As long as software development is done by mere humans. This assumption sets the bar (the worst case), and is a good principle for DX, as well as UX. The constrained nature of the language should allow for quick learning and proficiency. Complexity should lie in the system and domain, not the language. When the language restricts what can be done, it's easier to understand what was done (a smaller space of possibilities reduces ambiguity and increases predictability, which gives speed for everyone, at a small initial learning cost). The language should avoid Pit of Despair programming, and leave the programmer in the Pit of Success: where its rules encourage you to write correct code in the first place. Inspired by Eric Lippert, but also by Rust.
What are some alternatives?
average - Provides a (fake) monoid for calculating arithmetic means.
ekg-carbon - An EKG backend to send statistics to Carbon (part of Graphite monitoring tools)
aeson-json-ast - Integration layer for "json-ast" and "aeson"
aeson-serialize - Functions for serializing a type that is an instance of ToJSON
base-unicode-symbols - Unicode alternatives for common functions and operators
lrucaching - Haskell implementation of an LRU cache
argon2 - Haskell bindings to libargon2 - the reference implementation of the Argon2 password-hashing function