Well, Step is apparently just the Sequence-subset of FutureJS and FutureJS as a whole is mostly syntactic sugar and baseline infrastructure (Deferreds, Promises) without tackling the fundamental problem.
Quite frankly, I've been down that rabbit hole with Twisted which also has most of these primitives. More magic does not help!
I do not want to deal with 'Future-ish object for the purpose of synchronizing other Futures'. Just let me write my code in sequential order where appropriate - which is about 90% of the business logic.
I'll quote jerf from this thread:
You shouldn't even have to think about this, let alone argue which way is the best way to do it.
And Larry Wall:
The computer should be doing the hard work. That's what it's paid to do, after all.
Comments
Well, Step is apparently just the Sequence-subset of FutureJS and FutureJS as a whole is mostly syntactic sugar and baseline infrastructure (Deferreds, Promises) without tackling the fundamental problem.
Quite frankly, I've been down that rabbit hole with Twisted which also has most of these primitives. More magic does not help!
I do not want to deal with 'Future-ish object for the purpose of synchronizing other Futures'. Just let me write my code in sequential order where appropriate - which is about 90% of the business logic.
I'll quote jerf from this thread: You shouldn't even have to think about this, let alone argue which way is the best way to do it.
And Larry Wall: The computer should be doing the hard work. That's what it's paid to do, after all.