I disagree with these posts, because there are still a number things which jQuery handles which are not easy to replicate quickly unless you know the edge cases you need to handle. There is, however, a very major reason to avoid jQuery, and it has very little to do with features or file-size. jQuery is smothering your SPA's performance. I don't mean a little.
[/caption] Delivering a fast experience on the web usually involves reducing server response time, minification of CSS/JS/HTML and an optimisation of images and above-the-fold content. We can further minimize the latency caused by stylesheet loading by removing unused CSS rules delivered to the client. In this write-up, we'll take a look at build tasks you can use to remove unused CSS in your pages. Unused CSS is a particular problem when working with a heavy modern UI framework such as Twitter Bootstrap, Zurb Foundation or Adobe TopCoat. This is a problem that’s been previously highlighted by the PageSpeed team, who include removing unused CSS as part of their speed recommendations for the web: "Before a browser can begin to render a web page, it must download and parse any stylesheets that are required to lay out the page.