I&#x27;m 34, been developing web stuff for over 10 years now, and started using JQuery back when John Resig was still personally meeting &amp; greeting people who were using JQuery at meetups.<p>I&#x27;m pretty firmly in the &quot;You don&#x27;t need JQuery camp&quot;, and the reason is that you don&#x27;t need JQuery <i>now</i>.  It was an amazing piece of software when it came out; it made rich JS development not only practical, but easy, without worrying about cross-browser issues.  But it succeeded.  Resig&#x27;s goal - from very early on, at least as soon as he started to working at Mozilla - was to get JQuery baked into browsers, and he&#x27;s largely done that.  We got querySelectorAll.  We got a unified event model that all browsers support.  We got FormData.  We got a consistent box model, and consistent getComputedStyle() behavior.  We got animations and transitions, and the native versions even run on the GPU for fast mobile performance.<p>As a result, most of the problems that JQuery solved just aren&#x27;t problems in modern web development.  Cross-browser issues are minor and getting smaller every day.  Selectors are baked in.  Animations and transitions are CSS one-liners, rather than needing to spin up a setTimeout loop and manually calculate the delta in the property each tick.<p>That doesn&#x27;t deny the historical significance of JQuery, or just how much it improved web development back in 2007.  But we build apps for the world we live in <i>today</i>, and <i>today</i>, JQuery gives you some minor programming convenience in exchange for 30K of download size and a bunch of layout thrashing if you use its CSS or dimensions methods.