By mswatcher
via blog.parse.com
Submitted: Jan 30 2013 / 04:52
“Promises” represent the next great paradigm in JavaScript programming. But understanding why they are so great is no simple matter. At its core, a Promise represents the result of a task, which may or may not have completed. The only interface requirement of a Promise is having a function called then, which can be given callbacks to be called when the promise is fulfilled or has failed. This is outlined in the CommonJS Promises/A proposal
-
Square Libraries and Tools for Android Development
-
Calculating the perfect Tetris play: Part I
-
Being agile instead of doing agile
-
The Cloud Isn't a Beverly Hills Nose Job at a Tijuana Price
-
tmux article
-
From Patterns to Code: Coding Simple Event-Driven Components for Agile Software by Russ Miles (Podcast)
Add your comment
