> But it took a lot of work to convince people that it [JQuery] was unnecessary.
First it took about a decade of browser and ECMA very intensive development to actually make it unnecessary.
> it is becoming difficult to convince new developers that React may not be necessary for their next project.
Give it a decade for the web "components" to actually become composable and for inventive and useful native language built-in solutions to state management to happen before you start advocating people out of React. Until then telling people they might not need React is not a step forward but backward. Imagine people saying "you might not need jQuery" in times where IE reigned and browsers were wildly incompatible.
First it took about a decade of browser and ECMA very intensive development to actually make it unnecessary.
> it is becoming difficult to convince new developers that React may not be necessary for their next project.
Give it a decade for the web "components" to actually become composable and for inventive and useful native language built-in solutions to state management to happen before you start advocating people out of React. Until then telling people they might not need React is not a step forward but backward. Imagine people saying "you might not need jQuery" in times where IE reigned and browsers were wildly incompatible.