gotta-go-fast
infernu

gotta-go-fast | infernu | |
---|---|---|
2 | 2 | |
283 | 338 | |
- | - | |
0.0 | 0.0 | |
almost 2 years ago | about 6 years ago | |
Haskell | Haskell | |
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.
gotta-go-fast
-
Are there any cli typing test like monkeytype?
https://github.com/callum-oakley/gotta-go-fast (seems abandonned)
-
Package for writing an interactive command line tool
I would like to build a command line utility for practicing typing similar to https://github.com/callum-oakley/gotta-go-fast.
infernu
-
The TypeScript Experience
Or maybe a sound type system can only be achieved either by limiting JavaScript or with a different language that compiles to JavaScript?
-
Features of a dream programming language: 2nd draft.
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?
logging-effect - A very general logging effect for Haskell
ascii-art-to-unicode - Small program to convert ASCII box art to Unicode box drawings.
elm-repl
ekg-carbon - An EKG backend to send statistics to Carbon (part of Graphite monitoring tools)
base-unicode-symbols - Unicode alternatives for common functions and operators
hascard - flashcard TUI with markdown cards
pointfree - Maintenance of the pointfree Hackage package.
xkcd - Downloads the most recent xkcd strip
dag - A well-typed Directed Acyclic Graph in Haskell
quokka - Repository for Quokka.js questions and issues
bit-stream - Lazy infinite compact streams with cache-friendly O(1) indexing and applications for memoization
penrose - Haskell to JavaScript compiler, based on GHC
