I liked his examples, though I disagree with his conclusion (don't use jQuery). It seems like the real conclusions are:<p>1. understand the language you're using (this would solve the `bind` examples); and<p>2. learn how to use your libraries properly.<p>Otherwise, the "don't use $TOOL, because misuse can cause $BAD_THINGS" line of thinking is nearly limitless in its application (jQuery, cars, circular saws, ...).
Most of OP's complaints come from the misuse of JQuery, including compounded performance issues when paired with a SPA framework (in this case Ember, which IIRC has a dependency on JQuery either way). Slow + Slow = More slow.<p>Honestly it's a library. Use it, don't use it, replace it, it honestly isn't worth a million identical arguments. People like to use JQuery as a microcosm for bad javascript practices but guess what JQuery didn't make you do it! It's just a library.<p>There is no real reason to avoid JQuery. Sure you should, as a good developer, explore alternative solutions for different problem sets. Maybe those alternatives become the standard for your team, maybe they don't. But unless you made a meaningful discovery that can add to the conversation, you don't need to make another blog post about it. Ugh.
tl;dr: Use jQuery + plugins, if you want to do some small UI improvements in JavaScript and don't make it too complicated.<p>Learn a lot more about jQuery, if you write complex JS applications (like single-page apps) with the help of jQuery.
None of this is about jQuery - you can have the exact same problems in native JavaScript.<p>This page should be titled: "Don't forget to delete unused JavaScript things (nodes, events, etc)".