Airless energy return wheel
en.m.wikipedia.org1 ポイント投稿者 eulerphi2 コメント
export PATH=$PATH:/usr/local/rvm/bin/rvm
. /usr/local/rvm/scripts/rvm
. $REPO/.rvmrc
. $(rvm jruby-$JRUBY_VERSION do rvm env --path)
cd $REPO
bundle exec torquebox deploy
Definitely not ideal and I spent a large amount of hours figuring out how to use it non-interactively. I'm still somewhat worried that some things might go wrong if some of the code I didn't write in this repo attempts to call binaries directly. Basically with bundle exec --deployment, all gems are stored in $CODE/.vendor which is necessary to allow users to install their own gems, with the root installation. Bundle exec has to be used, I messed around with RVM wrappers, but they don't work with the --deployment bundler use.
It's surprisingly the location of the DOM elements. See here, I've swapped the two elements, and now the result is _backwards_
http://jsperf.com/always-return-on-jquery-events/21
Can anyone with knowledge of the webkit internal DOM id-based key/hashtable shed light on this?
I'm guessing that for the 2nd child, when it's propagating upwards, it has to hit 1 more element -- that is, if it must reach the first child to get the parent. I'd hope that the structure is more optimized than a simple crawl to the first node to go upwards.
EDIT: Actually, I'm wrong. I edited the test to have 6 divs, and re-arranged the order of the tests. The tests still come in performance-wise from first-to-last, first performing the best. I really don't know what to think now.