I smell NIH all over the post. This guy probably:<p>- Hasn&#x27;t been through hard deadlines, proof-of-concept software, silly client requirements (like IE8 support) and other things that need to be done quick and dirty.<p>- Hasn&#x27;t written against monolithic frameworks, legacy code or enterprise software. The web scene is fast moving, these software don&#x27;t. You have to make do with what is available, most of which are old code and frameworks.<p>- This guy probably hasn&#x27;t seen the horrors of the web past and hasn&#x27;t been burned for failing to make some functionality cross-browser friendly.<p>- Doesn&#x27;t have an idea of cross-browser support. How do you AJAX when `fetch` isn&#x27;t cross-browser yet? How do you deep-clone when Object.assign isn&#x27;t IE-friendly. Are you willing to waste time writing what libraries already do for you?<p>- Hasn&#x27;t written a large scale app. I&#x27;ve seen terrible things written in jQuery. How much more terrible would it be <i>without</i> it?<p>It&#x27;s not jQuery&#x27;s, or Bootstrap&#x27;s fault. It&#x27;s all about using the right tools at the right time the right way.<p>Besides, jQuery and Bootstrap both can be custom-built to what you need and not include everything. <i>But then, the author probably didn&#x27;t know that</i>.<p>There are also lighter libraries like Zepto and Pure, but the author <i>may have not known those as well</i>.