Joined July 2011
·
Posted to
DO NOT $('#foo a'); DO $('#foo').find('a');
over 1 year
ago
Maybe you could link to an actual http://jsperf.com/ link.
And maybe you'll see that the performance gain is worth only when you are doing billions of jQuery selects in a for loop.
So, if you're not doing it in a for loop then your wasting your time trying optimizing something that only happens once.
Achievements
376 Karma
35,481 Total ProTip Views
Altruist
Increase developer well-being by sharing at least 20 open source projects
Forked 20
Have an established project that's been forked at least 20 times
Raven
Have at least one original repo where some form of shell script is the dominant language
Honey Badger
Have at least one original Node.js-specific repo
Lemmings 100
Write something great enough to have at least 100 watchers of the project
Forked
Have a project valued enough to be forked by someone else
Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos
Epidexipteryx
Have at least one original repo where C++ is the dominant language
Charity
Fork and commit to someone's open source project in need
@turg0n Hey hi. I tried commander.js before diving into node's readline functions.
It turned out commander.js was buggy. When prompting, ̀return ̀ would not trigger end of prompt, needed to press ̀return ̀ twice.
All I needed was a simple prompt function. Did not want to debug a library that seemed not so up to date based on new node readline library. So made my simple function and voilà!
Now thinking to build my own simple node-input library that would prompt/confirm/choose only. No option parsing etc as commander.js do. There are already a lot of modules for that.
What do you think?