Hacker News Reader

Comment by qprofyeh | Hacker News Reader

Share the same sentiment. React has gotten weird. It feels like they took a perfectly done design and awkwardly pushed it over its boundaries. (They got away with hooks, but this time it’s different)

Funny thing is they say it’s for the DX to become more like PHP. But the PHP I remember was practical.

View on HN

For those that are not following very closely, what came after the “hooks” that took it too far?

Server components, which are in Next.js (using React's canary branch). Server components are not yet in official (i.e. non-canary) React, and the React team supports this move (as do I). I just wish that the tool that was so helpful with the "other" (100% client-side) React, "Create React App", was better supported these days.

Create React App is in a strange, pseudo-death state.

- It is not listed as an option for starting a new project in the React docs[0].

- The last release was April 12, 2022.

- The last time I created a new project with CRA, it printed a console log that claimed CRA was deprecated. However, the message seemed to originate from a dependency rather than CRA itself.

All this was enough to convince me to move to Next.js for future projects; though I find Next.js overcomplicated and full of things I will never use.

0 - https://react.dev/learn/start-a-new-react-project

I mentioned this upthread, but the "official" deprecation notice is this comment from Dan Abramov in a GitHub issue: https://github.com/reactjs/react.dev/pull/5487#issuecomment-...

Server side rendering / server components / pushing NextJS on everyone

Next.js and server side components

Reply on news.ycombinator.com