It seems JS developers are recreating the debates that were already had, numerous times, long ago.<p>Yes using a JS Framework is going to be slower than writing and optimizing code by hand. In the same way that you can do faster code in assembler than using any languages or that using GTK on top of X is going to be slower than writing directly to the graphic card.<p>Yet we still uses them because it mean less bugs (because you are not reinventing the wheel every time), it encourage code reuse, it add structure, allow other dev to easily enter the code and open you to a vast library of modules. But most importantly it allow shipping features faster and that&#x27;s where it impact the users.<p>Users care more about having an usable product than a fast one that does nothing (with some exceptions obviously). We can afford to optimize everything by hand and ship at the same time.<p>Sure, in some use-cases it will be too slow, but then you identify those particulars cases and you take your time to optimize them. Even by bypassing the framework if you need to.<p>But don&#x27;t decide to not use a framework because the general use case will be a bit slower.<p>Or as Knuth put it decades ago &quot;Premature optimization is the root of all evil&quot;<p>The complete quote being, because it&#x27;s relevant here:<p>&gt; &quot;We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%&quot;