I ran each test file 11 times, using:
Obviously, I changed the file name between iterations.
I removed 11.9 seconds, because these are setTimeouts in the actual tests, remaining with actual execution of promises time, and these are the final results (in seconds):
Native Bluebird Core-Promise
1.616 1.760 1.564
1.567 1.626 1.520
1.568 1.669 1.548
1.539 1.657 1.573
1.574 1.595 1.557
1.583 1.604 1.580
1.543 1.582 1.540
1.529 1.622 1.567
1.600 1.605 1.567
1.407 1.661 1.544
1.467 1.640 1.587
Unsurprisingly the native implementation won performance wise, but only less than 1% compared to the core-promise, but ~5% compared to bluebird. Also core-promise defaults to the native promises implementation if it's available, if you would use the exported Promise class (for tests I accessed the CorePromise implementation on purpose).
*Disclaimer* I am the creator of the core-promise, and yes I feel pretty good getting better performance than the "unmatched performance" of bluebird. :)
Do you want to live reload the browser as you edit and save using VIM?
Well wait no more, you can install the application by simply running:
Afterwards whenever saving, the page is automatically reloaded. Without any browser plugins.
(Press `ESC` followed by `:wq<ENTER>` to write the file, press `i` to start typing. When unsure press `ESC`.)
Add a line after all the Defaults with the following content:
For example on my system that would be:
Try to sudo with a wrong password and see what happens:
Yes, they change randomly.
When creating web applications, a lot of time is consumed switching back and forth between the code and the application itself. What if there would be an application that would refresh your browsers automatically?
Did your mind needs to stop to read (taken from ckeditor source):
Well you're not alone.
Stop using double negations, even if your code looks "cleaner", and refactor them to be single negations.
A simpler rule is never use negation variable names, so you don't run into issues like this. So don't use names such as: "noElementPresent", "dontRemove" or "notExisting".
For the previous example instead of "don't remove" go with "keep element", "keep", or something along those lines. Just search a thesaurus if you can't find a word.
Notice how readability is just so much better.
The one to rule them all. The browsers that is.
SharpKnight is an Android chess game.
MagicGroup is an eclipse plugin.