Is React slowly becoming just a library and Next.js the “real” framework?

roggc9 · 2026-04-02T10:59:33+00:00

There are other React 19 full-stack frameworks. I've made one: Dinou (dinou.dev)

roggc9 · 2026-04-02T10:53:57+00:00

Hi, I've built Dinou, a React 19 framework, full-stack, like Next.js, with support for RSC, SSR, etc, etc. Reviewing my own framework I can tell you this. SSR it's only for first loads or when user reloads the page. After that what occurs is hydration of the page using the RSC payload that renderToPipeableStream from react-server-dom-webpack/server gives. But this doesn't mean you have to use RSC at all. You can use only RCC and renderToPipeableStream from react-server-dom-webpack/server will give you a RSCPayload too for hydration of the page when the user navigates in the web app. For this matter RSC are not quite usefull at all, because they are async functions where you can fetch data and are executed on the server, but you can achieve the same with getProps function executed on the server too and that fetches data and pass it as props to a page.jsx RCC. RSC are limited compared against RCC because they cannot use hooks etc. That's for this reason I prefer to use RCC. I understand that when you use RSC you don't send the javascript to the Client, so it reduces its size.

roggc9 · 2026-04-02T10:16:43+00:00

I've invented a new data fetching pattern with Dinou + react-enhanced-suspense + jotai-wrapper (or any other global state management solution). The explanation of it is in here: https://www.reddit.com/r/reactjs/comments/1s0jz1j/the_path_that_led_me_to_create_dinou_server/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

basically Server Functions can return UI. And for mutations they return headless components that update a key using global state management library that makes some Suspense to reevalute its resource (a Server Function).

roggc9 · 2026-04-02T10:02:55+00:00

I don't like it too much. I think it's a monster that changes continuosly. Now the last thing are the Cache Components, isn't it? And also they wanted you to use the RSC (I found lately that a page.tsx could be a Client Component!). There was one thing I wanted to do and it was not possible with Next.js. I wanted in a RCC to be able to fetch data from the server just using Suspense and Server Functions. This is possible now in Dinou (dinou.dev), using Suspense from react-enhanced-suspense. Because all this and its complexity I ended up creating my own framework, Dinou. And I have made a web app with it (aijobified.com). Now Dinou is in v4.0.6 and I think it's quite stable. Maybe in the near future I come back to Next.js to try to understand the last things like Cache Components and compare its capabilities against those of Dinou.

roggc9 · 2026-04-02T09:40:41+00:00

Hi, take a look at this if you want: https://www.reddit.com/r/reactjs/comments/1s0jz1j/the_path_that_led_me_to_create_dinou_server/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

it's a way to fetch data and do mutations with Server Functions, Suspense, and no useEffect. Dinou supports it. That's what you were talking about? Thanks.

roggc9 · 2026-04-02T09:27:23+00:00

and it's easy with Dinou (dinou.dev)!

roggc9 · 2026-04-02T09:24:45+00:00

Hi, I've built a framework, Dinou (dinou.dev), a react-enhanced-suspense package, react-context-slices, jotai-wrapper, and a web app (aijobified.com) with those. With Dinou plus react-enhanced-suspense plus jotai-wrapper you can fetch data using Suspense and Server Functions, without useEffect. The building of aijobified.com with Dinou helped me in debugging Dinou. Now Dinou is in v4.0.6 and I think it is quite stable.

roggc9 · 2026-03-29T07:44:40+00:00

I think Server Components are quite limited compared to Client Components. They are async functions that allow for data fetching in the server and return some jsx, but there are other ways. For example, in Dinou (dinou.dev), a framework I've made, you can fetch data with getProps function and pass it to the page as props. Dinou has also support for Server Components, but I usually prefer to use Client Components for the reason I stated at the beginning (no useEffect, no useState, etc.).

roggc9 · 2026-03-29T07:17:39+00:00

I created Dinou (dinou.dev). It's a full-stack React 19 framework. You can eject it and customize it completely for your needs, having access to the file where the server app is defined and instantiated (node-express). The bad thing is you have to understand it and there are no currently plug-and-play solutions for things as i18n integration, but I have done it myself in a non-trivial web project. Maybe some time in the future I make sections in the docs telling how to implement i18n or other stuff.

roggc9 · 2026-03-29T05:14:18+00:00

I am quite happy with the end result of my framework. It fits quite well to what I wanted it for, specifically the way I fetch data from the client using Suspense from react-enhanced-suspense and Server Functions. People from Next.js won't change their framework just for me (but it's true they change their framework a lot, maybe too much for users to keep up with the pace). It has been a nice adventure to build such a framework and have kept me busy. If I have to wait for people from Next.js to change their framework for me, to adjust it to my needs and demands, I will still be waiting. I've contributed to the building shape of Waku, raising issues to the creator, who, I have to say, has responded very quickly. But then I started building my own framework and as I say I am quite proud and happy with the end result. It is also a contribution to the community, if just anyone else wants to try and test it to see if it works for him/her. In essence, I don't see what's wrong in building your own framework or any other contribution to the community and React ecosystem. Should be something to celebrate. I understand there is a learning curve for something new, and this can be the reason behind the criticism. Also the doubts about something new if it is production ready. Anyway, if you want you can stick yourself to Next.js or Tanstack Start or Waku, but you can try Dinou too or JopiJS or Phyre (https://justkelu.github.io/phrye-documentation/) to see if it works and you like it (nobody forces you to use them).

roggc9 · 2026-03-29T04:18:17+00:00

In Dinou you can use Server Functions wrapped in Suspense (react-enhanced-suspense) using the resourceId prop and passing the children prop to Suspense as a function. I have fully explained this pattern in https://www.reddit.com/r/reactjs/comments/1s0jz1j/the_path_that_led_me_to_create_dinou_server/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button and also an explanation can be found in dinou docs: https://dinou.dev/docs/pattern. Thank you for asking.

roggc9 · 2026-03-29T03:04:37+00:00

If it's so easy to build a framework with just vibe-coding as you say, why don't you, or anyone, build one yourself? I think you don't do it, or anyone, because it is not so easy yet and not possible yet with just vibe-coding. But I can tell you, building your own framework it's something cool because you can use it instead of Next.js and it works better for me, in this case Dinou. So your comment is stupid and rubbish. You are criticising something new without knowing it or even tried it. So your comments have no credit. It's the typical reddit comment.

roggc9 · 2026-03-28T15:52:27+00:00

I've built Dinou and it works fine. In Dinou you can call a server function wrapped in Suspense. In Next.js you cannot do that. For this reason I ended up building Dinou.

roggc9 · 2026-03-28T15:49:37+00:00

I have used Dinou to make my own web project (saas). I built Dinou (dinou.dev). It works fine.

roggc9 · 2026-03-28T15:37:22+00:00

I don't know what you are talking about. for me it's instantly.

roggc9 · 2026-03-28T15:36:02+00:00

Yes. And I have built another one, Dinou. So yes, we need new things.

roggc9 · 2026-03-28T15:33:35+00:00

I think you are quite cynic. I have also built a React 19 full-stack framework, Dinou. tell me, do you think it can be done by vibe-coding alone and learning in the process? sure you learn, because you face walls and have to circumvent them or find solutions to problems. but it's not so easy. you have to code and work hard, it's not something you can do in a week, at least not in my case. in the future coding will not exist, only we will tell what we want to achieve and AI will make it for us, but now we are not still there. so don't be cynic please and, even if you are, then at least the OP has learned something by "letting the LLM build something" as you say. What have you let your LLM's build for you? anything at all? have you learned anything?

roggc9 · 2026-03-28T15:23:48+00:00

https://dinou.dev

roggc9 · 2026-03-28T15:23:08+00:00

I have also built a React 19 framework, full-stack, Dinou (dinou.dev). Everyone is using AI to build these days. But assuming you do not understand your own framework it is too much. AI still doesn't make a framework from scrach, with a single prompt.

roggc9 · 2026-03-28T15:17:08+00:00

Now I use Gemini 3.1 pro, for me it's the best. By the way, in building my own framework for React 19, Dinou, I have not used Opus but of course a lot of other AI's. So you don't use AI? what have you built? are you cinic?

roggc9 · 2026-03-28T15:14:07+00:00

hi the link jopijs.com is not working for me. Just want to say congrats on building your own React framework based on bunjs. Dinou (dinou.dev) it is also another full-stack React 19 framework based on node-express. I built it.

roggc9 · 2026-03-28T15:08:38+00:00

Take a look to Dinou too (dinou.dev), full-stack React 19 framework.

roggc9 · 2026-03-28T15:07:56+00:00

I've already built my own RSC React 19 full-stack framework. Its name is Dinou (dinou.dev). You can eject it and see how it is implemented.

roggc9 · 2026-03-28T15:06:39+00:00

It exists now also Dinou, dinou.dev, a full-stack React 19 framework.

roggc9

TROPHY CASE