Benchmark: Angular clone vs Lodash clone (shallow) vs JSON Clone

HTML Preparation code:

<script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.8.3/angular.min.js"></script>
<script src='https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.15/lodash.min.js'></script>

Script Preparation code:

var MyObject = {
  description: 'Creates a deep copy of source, which should be an object or an array.',
  myNumber: 123456789,
  myBoolean: true,
  jayson: {
    stringify: 'JSON.stringify() method converts a JavaScript value to a JSON string....',
    parse: 'JSON.parse() method parses a JSON string...'
  }
};

var myCopy = null;

Tests:

Lodash clone (shallow)
myCopy = _.clone(MyObject);
Json clone
myCopy = JSON.parse(JSON.stringify(MyObject));
Angular copy
myCopy = angular.copy(MyObject);

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Lodash clone (shallow)
Json clone
Angular copy

Fastest: N/A

Slowest: N/A

Latest run results:

No previous run results

This benchmark does not have any results yet. Be the first one to run it!

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

LLMs can make mistakes. Check important info.

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

**Benchmark Definition**

The benchmark definition describes three different approaches to create a copy of an object: Lodash clone (shallow), JSON clone, and Angular copy.

1. **Lodash Clone**: The `_.clone()` function from the Lodash library is used to create a shallow copy of the original object.
2. **JSON Clone**: The `JSON.parse(JSON.stringify(obj))` method is used to create a deep copy of the original object by parsing the JSON string representation of the object and then creating a new object from it.
3. **Angular Copy**: The `angular.copy()` function (now deprecated in Angular 9+) is used to create a shallow copy of the original object.

**Pros and Cons**

Here's a brief overview of each approach:

1. **Lodash Clone (Shallow)**:
	* Pros: Fast, simple, and widely supported.
	* Cons: Only creates a shallow copy, meaning it only copies the top-level properties and not nested objects or arrays. This can lead to unexpected behavior if the original object contains complex data structures.
2. **JSON Clone (Deep)**:
	* Pros: Creates a deep copy of the entire object, including all nested objects and arrays.
	* Cons: Slower than Lodash clone due to the additional parsing step required.
3. **Angular Copy**:
	* Pros: Fast and easy to use, especially in Angular applications where `angular.copy()` is a built-in function.
	* Cons: Only creates a shallow copy, similar to Lodash clone.

**Library Usage**

In this benchmark, two libraries are used:

1. **Lodash**: A popular utility library that provides various functions for tasks such as cloning objects, manipulating arrays, and more.
2. **Angular**: A JavaScript framework for building web applications. The `angular.copy()` function is used in the benchmark to create a shallow copy of the original object.

**Special JS Features/Syntax**

None mentioned in this benchmark.

**Other Alternatives**

If you're looking for alternatives to these approaches, consider:

1. **Object.assign()**: A simple way to create a shallow copy of an object.
2. **Array.prototype.slice()**: Can be used to clone arrays, but not suitable for objects with complex data structures.
3. **Spread Operator (`...`)**: Can be used to create a shallow copy of objects by spreading their properties into a new object.

Keep in mind that the choice of method depends on your specific use case and performance requirements.

Related benchmarks:

Angular clone vs Lodash clone (shallow) vs JSON Clone (version: 0)

Comparing performance of: Lodash clone (shallow) vs Json clone vs Angular copy

Created: 3 years ago by: Guest

Jump to the latest result

Lodash clone (shallow)

Json clone

Angular copy

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

No previous run results

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