I like React. I utilize it for all my individual jobs and would like to suggest it for brand-new work efforts. Nevertheless, after the undesirable experience I had, I will not motivate utilizing it for business applications. Not once again.
Respectfully to OP, I want to offer my own anecdotes to the contrary. 2 of my last 3 positions have actually been at what I would think about to be “business”, and React was simply great for them.
His vision is to move a huge desktop WPF application to the web in the cloud. … He currently has an advancement partner in India, however they do not have experience in structure web applications. … Quick onboarding for brand-new staff member, specifically for the.NET designers dealing with the old desktop application
I believe OP has actually currently determined the most significant concerns at play. It seems like the designers needed to find out not just a brand-new structure, however the whole platform of web advancement in basic.
OP didn’t (almost) stop working due to the fact that of an intrinsic issue in React itself (as one may presume from the title). The issue was that the group needed to move their frame of mind from OOP to reactive elements, and it was intensified by doing advancement throughout time zones and cultures.
If the designers were currently contracted out, I’m nearly amazed they didn’t discover designers who were currently experienced in React to do the port. A React application would be extremely various structurally-speaking than a desktop application. The existing devs would have domain understanding, however a minimum of a few of them would or might construct the backend for the React frontend to speak to, and hand down that understanding at the same time.
( I.e. Why would you train oil employees to be astronauts rather of training astronauts to drill?)