I guess I don't understand the significant advantage this would provide. You can accomplish some of the same functionality with other control flow libraries. Also, I could see the future declaration, with potentially cascading effects, causing as much confusion in the code as callbacks.
The idea of continuations (which promises are) is to make an asynchronous control flow look like it is synchronous, but not become synchronous. More than anything, it is about readability and having a logical flow in the code.
I just see it as removing a layer of complexity... I don't really care for having PayPal functionality, and not having to worry about the monthly fee paid to you makes it easier on me and you. You get paid quickly, and I don't have to account for another fee. The 50 cents just becomes part of COGS.
Makes sense. I'm all for making things easier. There is no reason why I could not charge the 50 cents for Stripe charges immediately. And, then come back and charge 50 cents for any PayPal transactions (if any) at the end of the month.
Would be nice if they decided that cashflow forecasting (Microsoft Money and Quicken Online both did that well-ish) was important to add. That's the single reason I haven't gone with Mint.
I think the issue comes across pretty clearly in the initial conversations. If you're dealing with a client looking for the cheapest possible website, he's going to force the issue of price early on. If you're dealing with a solution-oriented one, there's some understanding of the cost to value relationship.
To me, that's the key. Value. A $10,000 website is a bargain if it allows them to bring in much more than that in new business or save more than that in costs. But to get that message across, you have to quantify and drive home the potential payoff.
I have both RamNode and Digital Ocean servers in production.
In terms of performance and cost, both are great. I haven't ever had any issues with Digital Ocean. With RamNode, they've had a couple of issues where there's been minimal downtime. And they had a breach back in June, but responded well.
I think I trust Digital Ocean more. The setup is easier and performance maybe slightly better.
I had to re-do our TeamCity integration when they stripped out the IIS Path property out of the project file in favor of publishing profiles. For a shop like ours, where we have lots of small projects, automating the deployment is pretty critical. I don't want to have to add 120 publish profiles when previously I could rely on the project settings.
Ultimately, we hacked together a fix, but I'm still wary of their changes.
Obviously that's not sustainable... but even the 60 hour version sounds pretty rough to me. Without a wife and kids, maybe. But I think if I tried this I wouldn't have to worry about a wife and kids anymore.
Am I the only one who works better and more efficiently when I have a little bit of a break in between?
>> "The Supreme Administrative Court of the Republic of Poland (Polish: Naczelny Sąd Administracyjny) is the court of last resort in administrative cases e.g. those betweens private citizens (or corporations) and administrative bodies. "
The point of Node is that it is asynchronous.