infernu
ramda
Our great sponsors
infernu | ramda | |
---|---|---|
2 | 80 | |
337 | 23,578 | |
- | 0.4% | |
0.0 | 6.6 | |
over 5 years ago | 9 days ago | |
Haskell | JavaScript | |
GNU General Public License v2.0 only | MIT 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.
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.
ramda
-
Tacit Programming
JavaScript is great for point-free programming! Make sure you check out Ramda.js https://ramdajs.com/
It’s fun in the sense that solving a puzzle is fun, but I avoid it for anything I need to maintain long-term.
But it’s good practice for understanding combinators which is useful for some kinds of problems.
-
Pipeline-Oriented Programming [video]
This is very cool. I remember I got sucked into things like Ramda going down this functional programming rabbit hole :-)
https://ramdajs.com/
-
Level up your Typescript game, functionally - Part 2
To create our pipeline, I'm going to use the pipe function from the NodeJS ramda library instead of building my own.
-
Level up your Typescript game, functionally - Part 3
Other libraries to check out are pratica and ramda
- Ramda: A practical functional library for JavaScript programmers
-
FP and JavaScript/TypeScript
I recently took ownership of the new types/ramda repo. This repo is re-exported by @types/ramda and is the first step to bringing type definitions for ramda in-house. We're already hard at work correcting major issues, adding full currying support, and general bug fixes
- [AskJS] Auto-Generated Documentation from JSDoc comments, nice modern themes?
-
When to use currying in JavaScript
I'm going to be honest. You probably don't need to use currying in JavaScript. In fact, trying to fit it in your code is going to do more harm than good, unless it's just for fun. Currying only becomes useful when you fully embrace functional programming, which, in JavaScript, means using a library like Ramda instead of the standard built-in functions.
-
No Lodash
Lodash gets so many things wrong I’d rather not see it in most projects. I appreciate a good utility library for JS projects but my go-to choice has to be Ramda[1]. Every function it exports is curried and works great with pipe which enables me to write highly reusable and composable functions in pointfree notation. I have never been as productive with lodash, and I find the functional style easier to read
[1] https://ramdajs.com/
-
Snap.js - A competitor to Lodash
Do note though that ramda is different from rambda. 👍 (Granted they are very similar!)
What are some alternatives?
ascii-art-to-unicode - Small program to convert ASCII box art to Unicode box drawings.
lodash - A modern JavaScript utility library delivering modularity, performance, & extras.
ekg-carbon - An EKG backend to send statistics to Carbon (part of Graphite monitoring tools)
RxJS
argon2 - Haskell bindings to libargon2 - the reference implementation of the Argon2 password-hashing function
Rambda - Faster and smaller alternative to Ramda
gotta-go-fast - A command line utility for practicing typing and measuring your WPM and accuracy.
immutable-js - Immutable persistent data collections for Javascript which increase efficiency and simplicity.
hascard - flashcard TUI with markdown cards
fp-ts - Functional programming in TypeScript
quokka - Repository for Quokka.js questions and issues
lazy.js - Like Underscore, but lazier