Ramda: A practical functional library for JavaScript programmers

• ramda

  82 23,750 7.3 JavaScript

  :ram: Practical functional Javascript

  

• InfluxDB

  www.influxdata.com featured

  Purpose built for real-time analytics at any scale. InfluxDB Platform is powered by columnar analytics, optimized for cost-efficient storage, and built with open data standards.

  

• fantasy-land

  21 10,076 3.1 JavaScript

  Specification for interoperability of common algebraic structures in JavaScript

  

  It was never really my jam, but I used to follow the up-and-coming fantasy-land specs with great interest. It just seemed like a sharp dedicated community of folks trying to figure out better fp & algebraic stuff. I'm not sure who trailed off - in general I feel like there's much less connection in tech world, that the tech twitter and every other ultra-active tech channel has somewhat decayed. https://github.com/fantasyland/fantasy-land

  Thanks for the links. I know I've seen @gcanti's name a thousand times already, but it's already quite murky to me what it was attached to. Something in this sphere.

• Immer

  145 27,487 7.2 JavaScript

  Create the next immutable state by mutating the current one

  

  I like immer for this kind of thing: https://github.com/immerjs/immer

  It gives you immutable updates without getting bogged down in FP abstractions.

• generator

  5 4 7.7 TypeScript

  Generator module. (by preludejs)

  

  I find straight forward, dedicated combinators much more readable and practical to use ie. for iterables (context where it makes a lot of sense) [0] example [1], runtime assertions (through refutations, which are much faster than combinators over assertions) [2], parser combinators for smallish grammars [3] etc.

  In many cases vanilla/imperative js is more readable and terse, no need to bring functional fanaticism everywhere, just in places where it gives true benefits and in form that can be understood by peers.

  Functional code can be beautiful and can also be unreadable/undebugable. Same with imperative code. It's great in js/ts you can pick approach where the problem is expressed more naturally and mix it at will.

  [0] https://github.com/preludejs/generator

  [1] https://observablehq.com/@mirek/project-euler

  [2] https://github.com/preludejs/refute

  [3] https://github.com/preludejs/parser

• refute

  3 9 5.9 TypeScript

  Refute module.

  

  I find straight forward, dedicated combinators much more readable and practical to use ie. for iterables (context where it makes a lot of sense) [0] example [1], runtime assertions (through refutations, which are much faster than combinators over assertions) [2], parser combinators for smallish grammars [3] etc.

  In many cases vanilla/imperative js is more readable and terse, no need to bring functional fanaticism everywhere, just in places where it gives true benefits and in form that can be understood by peers.

  Functional code can be beautiful and can also be unreadable/undebugable. Same with imperative code. It's great in js/ts you can pick approach where the problem is expressed more naturally and mix it at will.

  [0] https://github.com/preludejs/generator

  [1] https://observablehq.com/@mirek/project-euler

  [2] https://github.com/preludejs/refute

  [3] https://github.com/preludejs/parser

• parser

  4 5 7.8 TypeScript

  Parser combinators. (by preludejs)

  

  I find straight forward, dedicated combinators much more readable and practical to use ie. for iterables (context where it makes a lot of sense) [0] example [1], runtime assertions (through refutations, which are much faster than combinators over assertions) [2], parser combinators for smallish grammars [3] etc.

  In many cases vanilla/imperative js is more readable and terse, no need to bring functional fanaticism everywhere, just in places where it gives true benefits and in form that can be understood by peers.

  Functional code can be beautiful and can also be unreadable/undebugable. Same with imperative code. It's great in js/ts you can pick approach where the problem is expressed more naturally and mix it at will.

  [0] https://github.com/preludejs/generator

  [1] https://observablehq.com/@mirek/project-euler

  [2] https://github.com/preludejs/refute

  [3] https://github.com/preludejs/parser

• remeda

  12 4,395 9.4 TypeScript

  A utility library for JavaScript and TypeScript.

  

  Personally I just don't think Ramda fits really well with JavaScript's mutable and often object-oriented nature. It goes against the grain too much for my taste, and it doesn't work very well with Typescript.

  In a professional setting I will probably always reach for Lodash due to it's maturity and mindshare. Personally, though, I really prefer Remeda (https://github.com/remeda/remeda) as a pragmatic and flexible API.

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

Suggest a related project