162 karma · joined April 1, 2011
Firstly, I wanted to bill in multiple currencies according to where customers come from, and Chargebee required multiple API accounts, so that there could be no unified reporting of activity. Stripe, on the other hand, is perfectly happy with USD plans/subscriptions living alongside those in EUR or GBP.
Secondly, if you start with just Stripe, you can add other added-value providers like Chargebee on top later, but once you're committed to managing everything through those providers, it's hard to go back.
And finally, it would be easy to assume that you will need all that fancy Dunning process and workflow magic, but setting it up is an additional up-front time & complexity cost which might never pay for itself. Better IMO to start off simple, write a little code to track failed payments and expiring cards, and email the customers directly the old-fashioned way. This way, you're also connecting personally with your customers.
For this reason alone, the change seems like a big usability fail.
Priceless.
SPDY 2, that is. SPDY 3 will still be supported.
It's correct that we don't want our current packages to build off non-master tags or branches, and that's because we've a bigger picture in mind. It's a concrete goal of MELPA is to provide two parallel archives of packages: the existing one, filled with "bleeding edge" packages, and a new archive containing "stable" packages which have been built from the same upstream sources, but using existing version tags found there. We're making progress with this goal: see https://github.com/milkypostman/melpa/pull/1407, for example.
If we can pull this off, this will yield the best of both worlds: users will get known-good versions of packages, and at the same time they will be confident that the stable packages came from the upstream developer's source tree (which isn't at all assured with Marmalade). It will also make releasing a new stable package as easy as tagging a source repository.
Recent versions of `package.el` allow packages to be pinned to specific package archives, which lets those concerned about bleeding-edge breakage pick and choose between "stable" and "unstable" packages on a case-by-case basis.
There's an expectation that curated content should be a high-quality subset of the whole internet, and providing an endless stream of content undermines that expectation.
In short, it is no longer illegal to use what a policeman or court might judge to be "insulting words or behaviour".
That functionality has become indispensable to me, and I hate reading my timeline in other clients.