javascript-allonge
ramda
| javascript-allonge | ramda | |
|---|---|---|
| 1 | 81 | |
| 760 | 23,626 | |
| - | 0.2% | |
| 10.0 | 7.2 | |
| almost 4 years ago | 14 days ago | |
| JavaScript | JavaScript | |
| - | 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.
javascript-allonge
-
FP techniques that will help you write better JavaScript
I ran across this anecdote about how people don't know (or acknowledge?) the existence of the index argument of Array.map. This is a link to the manuscript of the well regarded book on JS FP techniques "Javascript Allonge". The index arg is not mentioned.
https://github.com/raganwald/javascript-allonge/blob/db7c435...
ramda
-
Top 20 Javascript Libraries on Github
Repository: 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/
What are some alternatives?
pythonic-ts - A collection of Python-style utility functions for iterators and collections
lodash - A modern JavaScript utility library delivering modularity, performance, & extras.
mostly-adequate-guide - Mostly adequate guide to FP (in javascript)
Rambda - Faster and smaller alternative to Ramda
caniuse - Raw browser/feature support data from caniuse.com
RxJS
immutable-js - Immutable persistent data collections for Javascript which increase efficiency and simplicity.
fp-ts - Functional programming in TypeScript
lazy.js - Like Underscore, but lazier
Sanctuary - :see_no_evil: Refuge from unsafe JavaScript
underscore - JavaScript's utility _ belt
mori - ClojureScript's persistent data structures and supporting API from the comfort of vanilla JavaScript