proposal-private-methods VS proposal-record-tuple

But with the new ECMAScript class fields proposal we can do this easily and gracefully by using private fields as seen below:

Private instance methods and accessors Class Public Instance Fields & Private Instance Fields Static class fields and private static methods

Don't forget that abomination of syntax which is https://github.com/tc39/proposal-private-methods

This is not currently true. But there are proposals, currently in stage 3 for allowing this.

Private instance methods and accessors

There is a proposal for private methods but its not yet standard. However, they are currently supported in chromium browsers and in firefox after enabling a flag. These, however, only work using the class syntax, not in constructor functions like that used in your example.

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.