4 ms·

> I personally don't like that direction so looking forward to exploring new frameworks. Why? React core has been exactly the same as it was ten years ago. Bui

> I personally don't like that direction so looking forward to exploring new frameworks. Why? React core has been exactly the same as it was ten years ago. Building a React SPA has not changed significantly, other than the growth in third-party libraries that complement the Core. Recent developments in React has been about enabling its usage in wider problem domains, but not at the detriment of its previous use cases, so why would that affect you?

technion 1y ago
Much of the official documentation now refers to server components as the "right" way to do certain things. Cra is end of life, with the replacement nextjs being heavily biased towards server components. Your tooling certainly has changed in that you won't use cra any more, and I wouldn't agree that this direction does not detriment previous use cases.
- math_dandy 1y ago
  I view create-vite-app with React presets as the spiritual successor of create-react-app, rather than NextJS.
- johnny22 1y ago
  I'd already switched to vite due to the lack of customization that one has with CRA.Even if create-react-app was still maintained, I'd never go back to it.
- arkaic 1y ago
  Vite all the way....until that gets deprecated and forced to move to nextjs
mvdtnz 1y ago
Really? So class components are still first class citizens and play well with existing ecosystem code?
- esperent 1y ago
  > So class components are still first class citizens Yes https://react.dev/reference/react/Component https://react.dev/reference/react/Component > play well with existing ecosystem code? That's not something the React team has any control over so it feels like an unfair complaint. However, besides external libraries that are specifically designed to work with hooks, I'd say quite a lot of things would still work. And you can always just use older versions of things, nobody is forcing you to upgrade. Anyway, React has been using hooks for about 6 or 7 years now. Not quite the ten years claimed in the previous comment but not so far off either.
  - jakelazaroff 1y ago
    > That's not something the React team has any control over so it feels like an unfair complaint. Sure it is — they could let you run hooks from within class components. Not only do they not allow that, they actively discourage you from writing class components in the documentation. Even if they didn’t have control over that, though, how does the complaint feel unfair? When I buy into a tool, I’m buying into the ecosystem as well. If the ecosystem moves in a direction I don’t like, that’s a strong disincentive to using that tool!
owebmaster 1y ago
> React core has been exactly the same as it was ten years ago Are we not considering Hooks core yet?
- 0xblinq 1y ago
  Hooks were introduced in 2018. We're in 2025. It's not 10 years yet, but we're pretty close to that. Yes, time flies.

technion 1y ago

Much of the official documentation now refers to server components as the "right" way to do certain things. Cra is end of life, with the replacement nextjs being heavily biased towards server components. Your tooling certainly has changed in that you won't use cra any more, and I wouldn't agree that this direction does not detriment previous use cases.

math_dandy 1y ago
I view create-vite-app with React presets as the spiritual successor of create-react-app, rather than NextJS.
johnny22 1y ago
I'd already switched to vite due to the lack of customization that one has with CRA.Even if create-react-app was still maintained, I'd never go back to it.
arkaic 1y ago
Vite all the way....until that gets deprecated and forced to move to nextjs

mvdtnz 1y ago

Really? So class components are still first class citizens and play well with existing ecosystem code?

esperent 1y ago
> So class components are still first class citizens Yes https://react.dev/reference/react/Component https://react.dev/reference/react/Component > play well with existing ecosystem code? That's not something the React team has any control over so it feels like an unfair complaint. However, besides external libraries that are specifically designed to work with hooks, I'd say quite a lot of things would still work. And you can always just use older versions of things, nobody is forcing you to upgrade. Anyway, React has been using hooks for about 6 or 7 years now. Not quite the ten years claimed in the previous comment but not so far off either.
- jakelazaroff 1y ago
  > That's not something the React team has any control over so it feels like an unfair complaint. Sure it is — they could let you run hooks from within class components. Not only do they not allow that, they actively discourage you from writing class components in the documentation. Even if they didn’t have control over that, though, how does the complaint feel unfair? When I buy into a tool, I’m buying into the ecosystem as well. If the ecosystem moves in a direction I don’t like, that’s a strong disincentive to using that tool!

owebmaster 1y ago

> React core has been exactly the same as it was ten years ago Are we not considering Hooks core yet?

0xblinq 1y ago
Hooks were introduced in 2018. We're in 2025. It's not 10 years yet, but we're pretty close to that. Yes, time flies.