I read the full post. Twice. There’s definitely some valid arguments there, though I feel it should not just be based on ReactDOM.render() . Taking a look at the React object itself, there is a heck of a lot more in there. One could argue that jQuery is consuming my code at some level too, yet we still consider it a library. Now I’ll admit it’s miles easier to define the difference between Angular and jQuery, but I feel that React essentially still does the same as jQuery, at a different level — the VDOM.

P.S. I used React inside Angular.js for 2 years on a daily basis as part of my job. It’s a stop-gap solution at best and to be used only if there’s no better option, you’re right. While it works, it comes with a plethora of issues nobody wants to deal with. 😃

Writer of code, blogs and things that live on the web. Pragmatic doer, Lego fan, Mac user, cool nerd. JavaScript and Flutter enthusiast. HMH.engineering editor.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store