Depending on what you are doing, you may have very little react-specific code in your application.
You have data fetching, caching, persistence, authentication, tons of things, not to mention business logic that needs to be implemented in just plain Javascript.
Then out of that process you may have workers or other async background jobs happening which should not involve React at all.
[0]: It may not be required, but it was created for a reason....
There are other templating systems you can use in React if you don't like JSX.
I've seen one codebase use direct calls to ReactDOM.createElement and there is a new hotness (which I can't think of the name of now) that replaces JSX with template literals, something like:
function NamePetList(props) {
return html`
<div>
Hello <b>${props.name}</b>!
<ul>
${props.pets.map(pet => html`
<li ${...pet.props}>${pet.name}</li>`
}
</ul>
</div>
`
}
which I really like.The library parses the strings to figure out which elements to create. Flow control and variables are just normal template literal arguments.
Personally I still use it, but I think it's fair to say that as much as JSX was created for a reason, it's made optional for a reason too.
Put another way: React calls your components, not you. You pass the component function itself to React.createElement, not its result.
JSX prevents you from being able to do this directly. For example, <() => "hello" /> is illegal.