I&#x27;m assuming you&#x27;ve looked at <a href="https:&#x2F;&#x2F;www.promisejs.org&#x2F;generators&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.promisejs.org&#x2F;generators&#x2F;</a><p>I somewhat agree,  prefer callbacks to promises, generators as I see it give you more control of what happens within a promise and how to deal with multiple promises being returned.<p>The danger I see with promises is they can be used incorrectly. The project I&#x27;ve taken over at work, the developer used a promise as a timer and littered watching the same promise all over the code using
``` 
Promise(functionToResolve).then(function()...
```<p>This means we never know where a function is being called from. I don&#x27;t think you could do something like this with callbacks, instead you&#x27;d have to do
```
function(callback(){
&#x2F;&#x2F; trigger your other methods here
}
```<p>but maybe I&#x27;m wrong, I never would have expected somebody to use promises in the way they are used here.<p>Like&#x27;em or not, they are here to stay, and some people like the more synchronous appearance of them and I believe when dealing with an array of promises, generators will provide more fine-grained control.<p>Keen to hear others thoughts though.