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