Joined July 2012
·
Posted to
Me, my self and that
over 1 year
ago
I believe the accepted convention is "that"
Achievements
634 Karma
59,428 Total ProTip Views
Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos
Kona
Have at least one original repo where CoffeeScript is the dominant language
Python
Would you expect anything less? Have at least one original repo where Python is the dominant language
Charity
Fork and commit to someone's open source project in need
Honey Badger
Have at least one original Node.js-specific repo
@rquinlivan Thanks for the comment. I certainly believe you should use on() where applicable, but it shouldn't be used as a simple replacement for ready(). Unless I’m mistaken, Even if your handler isn't manipulating the DOM the browser has to stop to download, parse, and execute your JavaScript before it can continue to load the rest of the DOM. Depending on your situation, you can actually degrade perceived performance by using on(). Obviously, if you need an event handler to be available before ready() fires then on() is the right choice. But, I think in many situations it’s best to load your JavaScript after everything else, and do stuff after the DOM is ready.