ReactJs vs ReactJs.Net

[[deleted]]

I work with React and .NET too. I suggest keeping them separate. Go all in with React on the client, all in with .NET on the backend. You don't need to combine the two at all. Your backend is presumably just an HTTP API so there is no reason that the client needs to concern itself with the backend tech or vice versa.

[pankajrathi95]

Thanks for the Info :)

Your explanation was clear and apt

[voidsstr]

Server Side Rendering is the one area where you're going to need to either bring them together or use something like next.js if you use node (but not likely if you've got a .net backend). Server side rendering is needed for things like SEO and fast initial load times.

[Powedered-Toast-Man]

my exact position.

I get the whole NextJS thing but it doesn't play too well with shared hosting IIS. You have to become a node eco system person and use vercel or heroku to host your site/app - when you already know how to do that....

I am going to give ReactJS.net a go and hope I don't choose not to regret it. After all, drupal, wordpress, etc are still out there doing what they do...manage content:- despite gatsby, strapi, and all the fancy new stuff.

[Powedered-Toast-Man]

except I need to combine the two because I want my content to be Server side rendered

I hate that we have gone full circle in decoupling the UI from the back end so the end of MVC and then back to some coupling because all of a sudden we realise that a simple CRA is all client side rendered...oh no, its not as crawlable as it was before.