I liked his examples, though I disagree with his conclusion (don't use jQuery). It seems like the real conclusions are: 1. understand the language you're using (this would solve the `bind` examples); and 2. learn how to use your libraries properly. 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, ...).
How to avoid common SPA pitfalls when using third-party plugins
11–20 of 41 posts
Re: How to avoid common SPA pitfalls when using third-party plugins
#12tl;dr: Use jQuery + plugins, if you want to do some small UI improvements in JavaScript and don't make it too complicated. Learn a lot more about jQuery, if you write complex JS applications (like single-page apps) with the help of jQuery.
I feel like SPAs are one of the most abused concepts on the internet right now.
A cloud-based 3D modeling software? Yeah, that definitely needs to be some form of SPA.
Your twitter clone, blogging engine, etc. not only doesn't have to be an SPA, but shouldn't be one because it creates horrendous UX.
Re: How to avoid common SPA pitfalls when using third-party plugins
#13This page should be titled: "Don't forget to delete unused JavaScript things (nodes, events, etc)".
Re: How to avoid common SPA pitfalls when using third-party plugins
#14Re: How to avoid common SPA pitfalls when using third-party plugins
#15Re: How to avoid common SPA pitfalls when using third-party plugins
#16tl;dr: Use jQuery + plugins, if you want to do some small UI improvements in JavaScript and don't make it too complicated. Learn a lot more about jQuery, if you write complex JS applications (like single-page apps) with the help of jQuery.
I feel like SPAs are one of the most abused concepts on the internet right now. A cloud-based 3D modeling software? Yeah, that definitely needs to be some form of SPA. Your twitter clone, blogging engine, etc. not only doesn't have to be an SPA, but shouldn't be one because it creates horrendous UX.
Re: How to avoid common SPA pitfalls when using third-party plugins
#17Re: How to avoid common SPA pitfalls when using third-party plugins
#18What was the fake reason to avoid jQuery?
Re: How to avoid common SPA pitfalls when using third-party plugins
#19Re: How to avoid common SPA pitfalls when using third-party plugins
#20Most of the advice sound like basic JavaScript - avoid things that prevent the interpreter from garbage collecting.
Things that ought to be fundamental, but which were left unlearned while the web was allowed to be lazy. With static pages, GC concerns weren't very large, because soon enough the user is going to click ahead to a new page and wipe the slate anyway.