StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Frameworks
  4. Javascript Utilities And Libraries
  5. Ramda vs lodash

Ramda vs lodash

OverviewDecisionsComparisonAlternatives

Overview

Lodash
Lodash
Stacks10.7K
Followers886
Votes3
GitHub Stars61.3K
Forks7.1K
Ramda
Ramda
Stacks492
Followers83
Votes3
GitHub Stars24.1K
Forks1.4K

Ramda vs lodash: What are the differences?

Introduction

In this Markdown code, we will provide the key differences between the Ramda and lodash libraries. Ramda and lodash are two popular functional programming libraries in JavaScript that offer various utility functions and methods.

  1. Syntax and Functionality: Ramda emphasizes functional programming concepts and provides a purely functional approach to data manipulation. It encourages immutability and offers a point-free style of programming. Lodash, on the other hand, provides a more imperative programming style and offers a wide range of utility functions for common data manipulation tasks.

  2. Currying and Argument Order: Ramda automatically curries its functions, meaning that they can be partially applied and composed easily. It also follows a consistent argument order where the data is passed as the last argument. Lodash, however, requires manual currying using the _.curry function and follows a different argument order in some cases, where the data is passed as the first argument.

  3. Modularity: Ramda is a highly modular library, with each function being imported individually. This allows for tree-shaking and reduces the bundle size by only including the required functions. Lodash, on the other hand, provides a larger monolithic library by default, but it also offers a modularity system where individual methods can be imported to reduce bundle size.

  4. Performance: Ramda is designed to favor immutability and purity, often sacrificing performance for better functional programming practices. Lodash, on the other hand, focuses on providing optimized and performant utility functions, sacrificing some functional programming principles for improved performance.

  5. API Design: Ramda's API is consistent across all its functions, following a "data-last" and curried approach. This makes it easier to compose and reuse functions in a functional programming style. Lodash, while also offering function composition, has some functions that don't follow the currying approach and have a different argument order.

  6. Concurrency and Asynchrony: Lodash provides various functions and utilities to handle asynchronous operations and concurrency patterns, such as _.map, _.filter, and Promise handling functions. Ramda, on the other hand, focuses more on pure functional programming and does not provide specific utilities for handling asynchronous operations.

In Summary,

Ramda and lodash differ in their approach to functional programming, syntax, modularity, performance, API design, and support for concurrency and asynchrony. It's important to analyze the specific requirements of a project or use case to determine which library best suits the needs and coding style.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Lodash, Ramda

Abigail
Abigail

Dec 6, 2019

Decided

Fast Healthcare Interoperability Resources (FHIR) provides standard data objects in JSON format for the healthcare industry. Since JSON objects are hierarchical and tree-like, we had a need to defensively 'pluck' fields from our JSON objects and do lots of mapping. We tried jQuery and Underscore and a few other technologies like FHIRPath; but Lodash has been the most well supported, works in the most contexts, has the cleanest syntax, etc. We particularly like the ES6 version of Lodash, where we can import the method names directly, without resorting to * or _ syntax. We got hooked on the 'get' function to defensively pluck fields from objects without crashing our user interface, and have found countless uses for the other lodash functions throughout our apps. Lodash is great for developing and optimizing algorithms.

38.3k views38.3k
Comments

Detailed Comparison

Lodash
Lodash
Ramda
Ramda

A JavaScript utility library delivering consistency, modularity, performance, & extras. It provides utility functions for common programming tasks using the functional programming paradigm.

It emphasizes a purer functional style. Immutability and side-effect free functions are at the heart of its design philosophy. This can help you get the job done with simple, elegant code.

Statistics
GitHub Stars
61.3K
GitHub Stars
24.1K
GitHub Forks
7.1K
GitHub Forks
1.4K
Stacks
10.7K
Stacks
492
Followers
886
Followers
83
Votes
3
Votes
3
Pros & Cons
Pros
  • 2
    Better than Underscore
  • 1
    Simple
  • 0
    Better that Underscore
Cons
  • 1
    It reduce the performance
Pros
  • 2
    Automatically curried
  • 1
    Point free programming
Integrations
JavaScript
JavaScript
No integrations available

What are some alternatives to Lodash, Ramda?

Underscore

Underscore

A JavaScript library that provides a whole mess of useful functional programming helpers without extending any built-in objects.

Deno

Deno

It is a secure runtime for JavaScript and TypeScript built with V8, Rust, and Tokio.

Chart.js

Chart.js

Visualize your data in 6 different ways. Each of them animated, with a load of customisation options and interactivity extensions.

Immutable.js

Immutable.js

Immutable provides Persistent Immutable List, Stack, Map, OrderedMap, Set, OrderedSet and Record. They are highly efficient on modern JavaScript VMs by using structural sharing via hash maps tries and vector tries as popularized by Clojure and Scala, minimizing the need to copy or cache data.

Vue CLI

Vue CLI

Vue CLI aims to be the standard tooling baseline for the Vue ecosystem. It ensures the various build tools work smoothly together with sensible defaults so you can focus on writing your app instead of spending days wrangling with config.

Luxon

Luxon

It is a library that makes it easier to work with dates and times in Javascript. If you want, add and subtract them, format and parse them, ask them hard questions, and so on, it provides a much easier and comprehensive interface than the native types it wraps.

Prepack

Prepack

Prepack is a partial evaluator for JavaScript. Prepack rewrites a JavaScript bundle, resulting in JavaScript code that executes more efficiently. For initialization-heavy code, Prepack works best in an environment where JavaScript parsing is effectively cached.

Blockly

Blockly

It is a client-side library for the programming language JavaScript for creating block-based visual programming languages and editors. It is a project of Google and is free and open-source software.

Cesium

Cesium

it is used to create the leading web-based globe and map for visualizing dynamic data. We strive for the best possible performance, precision, visual quality, ease of use, platform support, and content.

Factor

Factor

It is an extension-focused and universal Vue.js platform for professional front-end developers. It will help you launch apps that impress and astonish your clients and colleagues. No more re-inventing the wheel, or rewriting and refactoring where it's unneeded.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase