Small aside, getting rid of jQuery is kind of hard... I&#x27;m half surprised that no browser has taken the core of jQuery and simply integrated its&#x27; usage patterns in the browser at this point (considering everything else added to the DOM).<p>Dealing with the DOM isn&#x27;t nearly has hard as it has&#x2F;had been in the past, but it&#x27;s still a bit more complex than jQuery&#x27;s API...  You can start with document.querySelector*, but then if you need an array, you need Array.from the results, then you can each&#x2F;map&#x2F;reduce until your heart&#x27;s content... event binding is still quite a bit more verbose as well.  Not to mention unbinding&#x2F;cleanup when adding&#x2F;removing nodes.<p>In the end, half the time I check &quot;is jQuery in the project already&quot; then I&#x27;ll use it.  More often than not, it is... that is except in &quot;enterprise&quot; projects where &quot;enterprise&quot; architects and the minions of developers have managed to introduce 3-4 different copies of varying old&#x2F;ancient versions of jQuery and no idea which one is actually loaded.  Because it&#x27;s &quot;just the front end&quot; and have no concept&#x2F;concern for actual load&#x2F;performance... don&#x27;t think about capturing state properly, and get weird behavioral patterns as a result.<p>Sorry for the rant, it just irks me that people are so dismissive of the front end or capability that the web offers because much of it is so easy to get results.  On another note, if you get more into it, do yourself a favor and avoid Angular.