> If the widget had some internal element construction to do then yes, I would agree ...which covers most everything, really. Also, in the React world, if you

> If the widget had some internal element construction to do then yes, I would agree ...which covers most everything, really. Also, in the React world, if you just need to manipulate the data passed into a component, that's all pure JS. Only the component itself (with a reference to the passed-in data) would be JSX, which is distinctly more friendly to work with than string concatenation. (and I say that as someone that hates having a build step) > However, there is still value in being able to share the same html template across multiple models. ... > Now you're faced with having to copy/paste the same template over and over in React I don't think you understand the concept of a React component, or I've misunderstood what you are saying. Make that template once and just use it wherever needed! I have some complaints with React, but lack of reuse and JSX being worse than the alternatives are NOT among them.