You probably don't need a JavaScript framework
To begin, React isn&#x27;t a framework. It’s a tool. Would you compare a table saw to a workshop? That doesn’t make sense and neither does comparing React to a framework—especially if you’re saying you don’t need one.<p>Furthermore, using a virtual DOM is not the purpose of React. Virtual DOM is merely a part of how React works. People don&#x27;t buy cars to get an engine. They buy cars to get around places. People don&#x27;t use React to get a virtual DOM engine. People use React to make building and maintaining apps easier.<p>Let’s say you decide you’re smarter than everyone who worked on React or some other library, and you can build your app without them. Great, if you’re building a small app this is probably just fine. Scale your app up, however, and you’re going to end up with a framework anyway. The only difference is that it will be your own framework, and chances are it will be difficult to understand, hard to maintain, and full of bugs, and you may even be stuck with it because of how much it would cost to change.<p>Using libraries, or even frameworks, is how you leverage the collective intelligence of dozen, hundreds, or even thousands of very smart minds (a few of whom might even be smarter than you). Especially proven ones with many successful projects using them.<p>You’re welcome to give this up to be a cowboy, but me: I’ve been there, thought I was that smart, and realized how much better off I am by not trying to reinvent the wheel every time.<p>The rest of the article mentions other points which don’t seem particularly related to framework decisions to me at all, so I’ll let them be.