react-solid-state VS proposal-record-tuple

On one hand I agree with it, don't go with Solid and expect that you will 100% find a Solid job. On the other hand I think that unlike a lot of other frameworks, learning Solid could be useful even if you don't end up using it. You could even end up using Solid as a really good state management library for React https://github.com/solidjs/react-solid-state (at it's core Solid is just a state management library)

[2]: https://github.com/solidjs/react-solid-state

There's https://github.com/solidjs/react-solid-state for enabling Solid reactivity in React components. My plan is wire up a lot of my state management with Solid and that and then just continue using whatever React dependencies we're reliant on. If one of the Solid headless ui component libraries got mature enough, we could probably port completely then.

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.