Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React Labs: What We've Been Working On – February 2024

react.dev

Post reply on HN
Print view View original

11–20 of 130 posts

Re: React Labs: What We've Been Working On – February 2024

#11

Post by rozularen »

fabian2k wrote: post #8
hyfgfh wrote: post #2

So thats why CRA has been left to die?

CRA was never a fully official project, though there was a lot of confusion around that. It was in a weird semi-official state, it certainly had the endorsement of the React team initially but it didn't have actual resources from Meta behind it. CRA was useful when it first appeared because the whole space was a big mess. But it very quickly outlived its usefulness, and its approach was really problematic in my opini…

I mean, the CRA repo is under facebook org in github

Re: React Labs: What We've Been Working On – February 2024

#12

Post by unkulunkulu »

fabian2k wrote: post #8
hyfgfh wrote: post #2

So thats why CRA has been left to die?

CRA was never a fully official project, though there was a lot of confusion around that. It was in a weird semi-official state, it certainly had the endorsement of the React team initially but it didn't have actual resources from Meta behind it. CRA was useful when it first appeared because the whole space was a big mess. But it very quickly outlived its usefulness, and its approach was really problematic in my opini…

my 2c: still does the job without ejecting on my small project. Just reading your comment made me happy I don’t spend time thinking about webpack configuration

Re: React Labs: What We've Been Working On – February 2024

#13

Post by udbhavs »

Learning about the auto-memoization feature when it was called React Forget made it seem like a pretty natural extension of the functional component paradigm - separating out and memo’ing parts within components based on info that’s trivially available at compile time (maybe not trivial, I’m not sure how much work is being done by the compiler here). Is this something that could be implemented as a language-level feature for some “dedicated” language for writing functional reactive UIs? Languages like ReasonML are meant to map more nicely to React’s model because of their expressiveness, but I wonder if it could be taken further.

Re: React Labs: What We've Been Working On – February 2024

#14

Post by preommr »

> One way to think about this is that React currently re-renders when object identity changes. With Forget, React re-renders when the semantic value changes — but without incurring the runtime cost of deep comparisons.

There's got to be another word for 'magic' to describe this kind of behavior because this is on a whole other level. People complain about observers, or transpiling being too magical, but at least those are straightforward in principle. I can see Rich's video on how svelte works and more or less get it, it's just that it happens implicitly. Semantic value here would depend entirely on the data type; I have no effective way of being sure of what is being implicitly generated.

Re: React Labs: What We've Been Working On – February 2024

#15

Post by fabian2k »

unkulunkulu wrote: post #12
fabian2k wrote: post #8

Earlier quoted context omitted.

CRA was never a fully official project, though there was a lot of confusion around that. It was in a weird semi-official state, it certainly had the endorsement of the React team initially but it didn't have actual resources from Meta behind it. CRA was useful when it first appeared because the whole space was a big mess. But it very quickly outlived its usefulness, and its approach was really problematic in my opini…

my 2c: still does the job without ejecting on my small project. Just reading your comment made me happy I don’t spend time thinking about webpack configuration

Until you run into any problem that you need to debug with the build process. And there are more problems today because CRA is not maintained well now.

The tools got much better, it's much easier to just set up a basic Webpack or Vite setup today compared to when CRA was originally created. And the simple configs are much simpler to debug and understand when something doesn't work as expected.

Re: React Labs: What We've Been Working On – February 2024

#16

Post by unkulunkulu »

fabian2k wrote: post #15
unkulunkulu wrote: post #12

Earlier quoted context omitted.

my 2c: still does the job without ejecting on my small project. Just reading your comment made me happy I don’t spend time thinking about webpack configuration

Until you run into any problem that you need to debug with the build process. And there are more problems today because CRA is not maintained well now. The tools got much better, it's much easier to just set up a basic Webpack or Vite setup today compared to when CRA was originally created. And the simple configs are much simpler to debug and understand when something doesn't work as expected.

thank you, will keep this in mind if problem arises, maybe the best route would be to reset the build system

Re: React Labs: What We've Been Working On – February 2024

#17

Post by hyfgfh »

azangru wrote: post #7
hyfgfh wrote: post #2

So thats why CRA has been left to die?

What's the connection? Also, take a look at this response from 2021: "Like I said earlier, it was always the intention that we're not going to be able to work on it full-time... [I]t was intentionally designed for this kind of sporadic development. We would get critical fixes out as soon as posible, but overall, starting with 2.0, it's mostly in maintenance mode and does not strive to be the best tool for production…

A new solution could replace some of the tools we use today, making it obsolete and not worth maintaining in the future.

Make sense, but the lack of an "oficial" solution doesn't help https://react.dev/learn/start-a-new-react-project

Re: React Labs: What We've Been Working On – February 2024

#18

Post by throwaway220033 »

The goal behind "hooks" was to make React simpler for beginners. I build client-side apps since 2007, and React is getting too magical and complex for even for me. The NextJS influence is really making things worse, "use server" "use client" tags do not scale at all. The project clearly lacks mission, goal, leadership and direction. I'll use Preact in the next projects.

Re: React Labs: What We've Been Working On – February 2024

#19

Post by hyfgfh »

fabian2k wrote: post #8
hyfgfh wrote: post #2

So thats why CRA has been left to die?

CRA was never a fully official project, though there was a lot of confusion around that. It was in a weird semi-official state, it certainly had the endorsement of the React team initially but it didn't have actual resources from Meta behind it. CRA was useful when it first appeared because the whole space was a big mess. But it very quickly outlived its usefulness, and its approach was really problematic in my opini…

> CRA was useful when it first appeared because the whole space was a big mess. But it very quickly outlived its usefulness, and its approach was really problematic in my opinion. The config was too complex to eject and modify compared to what you could do yourself with Webpack directly.

Yes agree, but writing and marinating config for multiple projects just don`t scale. Not to mention we need something dirty and fast.

Re: React Labs: What We've Been Working On – February 2024

#20

Post by cal85 »

Can anyone clarify how the compiler would fit into the workflow? Are we talking some kind of CLI that takes a JSX/TSX entry point as input and outputs a compiled JS bundle, like a replacement for Webpack/Rollup etc. but more specialised to optimise React code? Or something more fine-grained that operates on a single component/module at a time? Or something else?
Post reply on HN