Benchmark: Lodash.get vs Property dot notation - 2 deep

HTML Preparation code:

<script src="https://cdn.jsdelivr.net/lodash/4.16.0/lodash.min.js"></script>

Script Preparation code:

var person = {name: 'Frederick', lastName: { picture: 'pretty' }};

Tests:

Lodash get
_.get(person, 'lastName.picture');
Native
person?.lastName?.picture

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Lodash get
Native

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 2 months ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36

Browser/OS: Chrome 147 on Mac OS X 10.15.7

View result in a separate tab

Native

103.7M/s

Lodash get

7.9M/s

View exact numbers

Test name	Executions per second
✓ Native	103,664,304 Ops/sec
Lodash get	7,879,124 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

LLMs can make mistakes. Check important info.

Let's break down the benchmark and explain what's being tested.

**Benchmark Overview**

The benchmark compares two approaches to accessing nested properties in JavaScript:

1. **Lodash.get**: This is a function provided by the Lodash library, which helps with deep object access. It takes three arguments: the object to access, the property path (as an array of strings), and the value to return if the path doesn't exist.
2. **Property dot notation** (also known as chaining): This is a shorthand way of accessing nested properties using the `.` operator.

**Options Compared**

The two options being compared are:

1. Using Lodash.get with a specific property path
2. Using property dot notation to access the nested property

**Pros and Cons**

**Lodash.get**

Pros:

* Provides a safe and predictable way to handle missing property paths, reducing errors and exceptions.
* Allows for more control over the execution order of methods.

Cons:

* Adds an extra dependency on the Lodash library.
* May introduce additional overhead due to function call and argument passing.

**Property Dot Notation**

Pros:

* Lightweight and simple, with no dependencies or overhead.
* Fast and efficient, since it's just a simple property access.

Cons:

* Can lead to errors if the property path is invalid or missing.
* Less predictable behavior for complex nested objects.

**Special JS Feature/Syntax**

Neither of these options rely on special JavaScript features or syntax. However, using Lodash.get does involve creating an array of strings representing the property path, which might be seen as a "feature" by some (although it's more of a quirk).

**Library**

The Lodash library is used in this benchmark. Lodash provides a set of useful functions for tasks like:

* Working with arrays and objects
* Handling collections and iteration
* Utility functions for dates, strings, numbers, and more

Lodash is widely used and has many features that make it a popular choice among developers.

**Other Alternatives**

If you don't want to use Lodash, other alternatives for accessing nested properties include:

1. Using the `in` operator to check if a property exists, followed by bracket notation (`[]`) to access its value.
2. Using a library like jQuery or VanillaJS, which provide similar functionality.

However, these alternatives may introduce additional dependencies, overhead, or complexity compared to using Lodash.get or property dot notation.

**Benchmark Results**

The latest benchmark results show that the **Native** (property dot notation) approach is slightly faster than the **Lodash get** approach. However, this result might vary depending on the specific use case and environment.

Overall, the choice between Lodash.get and property dot notation depends on your project's requirements, personal preference, and performance considerations.

Lodash.get vs Property dot notation - 2 deep (version: 0)

Comparing performance of: `Lodash get vs Native`

Created: 4 years ago by: Registered User

Go to the latest result

Lodash get

Native

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

Lodash.get vs Property dot notation - 2 deep (version: 0)

Comparing performance of: Lodash get vs Native

Created: 4 years ago by: Registered User

Go to the latest result

Lodash get

Native

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

Related benchmarks

Comparing performance of: `Lodash get vs Native`