this is handy, however, if I'm understanding correctly, this would remove idempotency from your functions, which is a tradeoff like everything else.
I like the context idea, might make it easier to test too
Thanks for the vid! 🎉
carlosconejo
Interesting. Never heard of that. Looks like node's still has some interesting tricks
gilbertsenyonjo
Woww. Best explanation ever. Thanks Wes Bos!
gilbertsenyonjo
I‘m wondering if it would be possible to implement the same behavior with ES6. The storage object must have some kind of a register with the different states from the different stacks it started from. The function „three“, when called asynchronously, must then be able to be identified with it‘s origin stack (id) in order to get the right „register“ from the storage object when calling „getStorage“. While writing this, it seems not possible to do with the current available features (e.g. ES6).
arber
What's the difference with a global variable?
hfyaer
Bro, try to use a lower voice, that intro is insane..