I don't think React will be replaced for a very long time. The only library that has somewhat similar adoption rates to early React is Vue. I personally prefer Vue over React and I use it at work. But I would be happy using React as well if the choice was given to me. Vue3 + Composition API just makes sense to me.

Vue 3 + pinia is simply an amazing experience. Nothing is shoved down your throat

I tried getting back to React but Vue makes so much more sense. Feels like in the old days because all you do is write your code instead of dealing with a library and its ways.

Absolutely agree! Vue + Pinia = This is the way ©

Sanity hopefully

It'll be a long time before something comes along and dethrone react. React ecosystem is too vast and the community is large and engaged. Nothing comes closer to React atm.

Other than that, prob. lit-dev (with time).

> Other than that, prob. lit-dev (with time).

Yes. Nothing excites me more than web components and moving closer back to the browser. Somehow, it feels more exciting that server components, signals, compilers, resumability, etc. etc.

Succeed implies that it reigns supreme. But Vue and Angular has been significant for a long time now.

https://survey.stackoverflow.co/2022/#section-most-popular-t...

My bet for next-gen frontend tech is on svelte and SolidJS. They are faster, lighter and their tooling scene isn't as fragmented.

Looks like jQuery might get a comeback before vue and angular do anything based on that graph

Sure, if you consider 18% and 20% as doing nothing.

In my opinion? GTK on Wayland under WebGPU. You laugh now...

2030 will be the year of the linux desktop

To de-throne React, React would have to stop de-throning itself.

I do think the future of DOM based diffing is no longer going to use a Virtual DOM. Svelte has shown the way. It just has to be moved into React (or a React successor).

I also think the future of Components is to use async/await more. Where each await point is assigned a fallback component e.g. <Loading /> or something.

React also needs to figure out Hooks a bit better, and see if there is a missing language feature that can be pushed to simplify that concept.

If something (including React) is able to do those three things, while also keeping/improving the React DX (markup and logic together, uni-directional dataflow, hook like annotations that can interoperate with each other), it'll likely de-throne React.

Have you seen React Server Components? You mark a component as `async`, and then you `await` some Promise inside of the component to fetch data. The fallback points are declaratively defined through React Suspense. For example:

<Suspense fallback={<LoadingSkeleton />}>

  <MyComponent />

</Suspense>

Where your Server Component then looks as follows:

async function MyComponent() {

  const data = await db.get('...')

  return ...

}

https://nextjs.org/docs/getting-started/react-essentials

Yes, aware. Its cool, but the ergonomics feel very much the way I felt about Node.js with callbacks.

There is a different type of delight that comes from the ergonomics on async/await. This is the big jump React Suspense also needs to make. I am not smart enough to suggest anything here tho. I just know the framework (including React) that can give me that async/await delight while using Suspense will dominate!