This is something we experienced on The Wedding Favor. It was a trade-off we were aware of. On the other hand, it did trouble me that we were able to transfer money same-day to Chase bankholders with Balanced. It sounds great, but somewhere along the line that means that Balanced was "floating" our credit card charge and fronting the money to pay out to the end-recipient. While I appreciate this, and we benefit from very low chargeback rates (our users are friends and family), this seemed like a "too good to be true" risk.
In Stripe's case, you can make the business choice in your logic to pay out quicker to your end user, so long as you understand the risks (which you assume) and keep a comfortable account balance to cover it. Payouts to you, the Stripe account holder, is another matter!
Right, so the important thing to keep in mind (and this is different from Balanced), is that you are making a standard Charge object. It's business as usual.
When you pay money out to users, it is deducted from your Stripe balance. In that sense, the initial charge, and the transfer later, are not explicitly connected to each other. It's up to you to persist some business logic on the application side.
In our case, we build in Stripe's fees (the standard 2.9% + $0.30) and make an assumption about our transfer fees (25 cents per transfer) to make sure we come out on top. The payer (when we create the Charge object) is paying this fee.
That way, when I gift money to a couple, they are receiving EXACTLY what I intended to send them. We don't want the couple feel in any way like there's a "gotcha" — someone sent you $25, but you can withdrawal only $22! We are, of course, transparent to the payer about the additional fees they're covering.
We let users withdrawal their full amount. This is in part to encourage fewer transfer fees, but it also simplifies things for our end-user.
It's been great to work with Stripe. I can't say enough about the quality of their staff and the love and care they put into their API. It's something we should all appreciate and replicate.
Personally, I have had pretty terrible experiences with CloudFlare. Specifically, downtime at the DNS level and no options to keep a site up. This was last year - but it was an abysmal experience and a lot of unhappy customers in their support forums.
Amazing. It's impressive how forward-thinking his final thoughts on. So often in history we can't see how important something is at the very beginning of the story.
If you honestly think HN is a model of good design, you're a purist in the worst sense. HN isn't even responsive. I love this place, but that's absolutely ridiculous. They might as well throw in a free AOL disk.
I can say confidentially I would NEVER pay a monthly subscription for a freaking email program. You've got to be kidding me if this is your "solution."
Here's the lesson and Apple cannot fix this: indie developers can be swayed and pulled away by big companies like Google. Sparrow made the decision for themselves - not because of some inherent flaw in Apple's app economy.
Here's the other lesson for all of you: guess what? An (arguably) great app has just vanished from the ecosystem. Go create your own! There is obviously a gap to fill now. Make something better than Sparrow.
And when Google comes knocking, say no. Stop whining.
It doesn't change the fact that you're taking his words out of context. And you can't start a company to stop another. I still don't know what it is you're actually building or why it's worth a half million dollars. This isn't public funding when your "backers" don't get to own a piece of the business. This is just a well-orchestrated (?) pre-order.
Cringely, I thank you for Triumph of the Nerds, but in general you're full of shit. I don't blame Apple for not wanting to "promote" and pump up a movie of their recently deceased founder, so that you can make money off it.
I'd love to hear about a PERSON who routinely went out of their way to overpay for a service. When was the last time you arrived at a store, saw a shirt, and said, "I'd like to pay you an extra $10 for this shirt because I believe in what you're doing."
Never.
For that matter, when was the last time you called up the IRS and said, "Dammit America, you're doing such a good job, I'm sending an extra $5,000."
Never. In fact, the most you or I have ever given extra is the $3 election fund.
Let's stop joking around, people. Companies, like people, are going to find ways to pay as little as possible, so long as it's legal. Let's stop blaming Apple and blame ourselves: reform the tax code to be simple, fair, and progressive.
"Haiku is probably the best positioned to challenge the mainstream operating systems like Microsoft Windows and Mac OS."
This is an absurd statement. Stop wasting time solving problems that don't exist for 98% of the market. "More choice" is not a better than if the choices suck.
"Within 20 seconds or so of restarting, the machine was chugging away with all of its media files in the place they were when they were halted, as if nothing had happened."
This was really cool in the early days of BeOS. But that was more than a decade ago.
People of earth: there is a talent crisis right now. The world needs great developers to build awesome apps for a whole new class of machines. If you feel an urge to "start from scratch" — help rebuild everything for mobile. It's a big job, there are too many projects and not enough developers, and you'll be contributing to a seismic shift in computing.
Stop solving problems that don't exist for most people. Build apps that people will use. Do big things that address 98% of users. These guys clearly have dev chops that I admire, so don't waste them on a project like this.
In Stripe's case, you can make the business choice in your logic to pay out quicker to your end user, so long as you understand the risks (which you assume) and keep a comfortable account balance to cover it. Payouts to you, the Stripe account holder, is another matter!