proposal-record-tuple VS lodash

relevant issue, which is at the crux of this problem: https://github.com/tc39/proposal-record-tuple/issues/387

There are still so many basic things that aren't in the JS stdlib, though. A good example is Map - if you need to use a tuple of two values as a key, you're SOL because there's no way to customize key comparisons. Hopefully we'll get https://tc39.es/proposal-record-tuple/ eventually, but meanwhile languages ranging from C++ to Java to Python have had some sensible way to do this for over 20 years now.

If you’re reaching for structuredClone, what you really want is native immutable Record and Tuple syntax, and the companion “deep path properties” syntax which allows for efficient and ergonomic immutable updates:

- https://github.com/tc39/proposal-record-tuple

It will be called "record" in JavaScript which will swing the popularity back the other way I guess (currently a language proposal)

I suspect considering the strong desire to maintain consistency with JavaScript, we will eventually see something that when the Record proposal passes through tc39

I hope the Record and Tuple proposal makes it through

I mean, I'd love some real immutable/persistent data structures in JS by default, or even some Immer-like syntax sugar. Something like the record/tuple proposal would be awesome.

This will become very useful once Records and Tuples are a thing, because it allows you to store object references in a record/tuple (which by definition can only contain primitives).

Record and tuple is at stage 2

Also, js has an ongoing immutable value data types proposal.

Let’s make sure that we can packages and run code. We will install lodash, call a function from it, and print the output.

Lodash.js is like the Swiss Army knife for JavaScript developers. Need to manipulate data structures or dabble in functional programming? Lodash is here to save the day with its arsenal of utilities. It's all about making your code cleaner and your life easier, which is probably why big guns like Google and Airbnb have it in their toolkit.

lodash - utility library enabling things like deep object comparison that aren't easy to do with javascript out of the box. docs

Lodash is a widely used JavaScript utility library that provides a plethora of functions to simplify common programming tasks. From manipulating arrays and objects to handling edge cases and implementing functional programming paradigms, Lodash offers a comprehensive toolkit for JavaScript developers. In this beginner's guide, we'll learn how to get started with Lodash and leverage its functionality to write cleaner, more efficient, and more maintainable code.

5. Lodash

If you want even more sophisticated equality checks like deep comparisons, there's the: lodash.iseQual library that'll do this for you out of the box. At least now you do have a bit of clarity on what's happening under the hood, so there's no harm in using a library.

It's also important to ensure that you're importing libraries correctly, so webpack can perform tree shaking effectively. For example, let's import lodash, as follows:

Lodash is awesome! It’s a JavaScript library that helps you do many things with data. You can use Lodash to manipulate arrays, objects, JavaScript strings, numbers, and more. It’s easy to get Lodash in your project. You can use npm or a CDN to install and import it. Here’s how:

Think of RxJS as Lodash for events.

lodash and You Might Not Need Lodash