reactjs.org VS proposal-record-tuple

yes, he advocated for Vite in his pr: https://github.com/reactjs/reactjs.org/pull/5487

There have been several calls recently to remove the CRA recommendation, perhaps most notably from popular Twitter use and YouTuber Theo (t3.gg) whose pull request on the reactjs project recommending the replacement of CRA with Vite went viral on Twitter. This sparked heated criticism of CRA, including its perceived lack of features (such as native support for TypeScript or popular CSS library Tailwind), size, performance, and more.

It’s built on Next with tailwind. Check out the beta directory here: https://github.com/reactjs/reactjs.org

Not Docusaurus, but the source is here:

https://github.com/reactjs/reactjs.org (currently in the "beta" directory)

This came up a couple of weeks ago due to a PR opened on the CRA repo asking to kinda deprecate it as the main choice for new React projects. I couldn't help but share my opinion on this as well:

https://github.com/reactjs/reactjs.org/pull/5487#issuecommen...

I remember submitting the full link. Dunno why it was edited

More specifically, the comment: https://github.com/reactjs/reactjs.org/pull/5487#issuecommen...

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.