We are currently working on a new version of our Checkout product[0] and would love feedback. We are working on making the simplest drop-in integration to get up and running on Stripe, and we support Stripe Billing! Send me any thoughts you have (matt at stripe).
It's a great trend going forward to see companies becoming more open about the code they write, it helps get a third party perspective on what you're building. Balanced has done a good job at documenting and keeping their code clean enough that the barrier to contribution is as low as you can ask for on GH.
I'm not sure '40% higher conversion rates' means anything pertinent. If it directly correlates to a company's revenue, this is fantastic. However, if it also contributes to a higher fraudulent payment rate (say we are funding loans, or performing a transaction where payment fraud tends to be higher), it must be taken into consideration and weigh how much the company will pay for each individual customer support case versus revenue accrued from each conversion.
That aside, customer data here is not only used for simply 'making the payment' as the writer says. This is a huge over-simplification of the problem, the payment gateway for the transaction to detect AVS and CVV is a /last ditch effort/ to catch fraud. The other fields could be used for other services that detect fraud such as ID Analytics, Experian, etc. and ultimately help mitigate credit and fraud risk for the company.
This price model will motivate the developers to create products that exactly tailor all the needs of their users, and the users could potentially (and probably will) save money buying a subset of the products they deem necessary. A flat fee will make the developers focus on top X priorities, leaving a segment of the user base possibly out of luck.
The call to default _uuids API call generates random UUIds, however you could override the call in the _config to have a different algorithm field, one that potentially could call "utc_random" still while appending a timestamp in the string to sort by later. Was this thought about when CouchDB was potentially considered?
I'm curious - would it be inefficient to use something that could efficiently compile Ruby into PHP such as Fructose, and then use HipHop for PHP from Facebook to compile the PHP into C++? So far I don't see a lot of tools that utilize the Ruby->C++ direction, and much work has gone into HipHop for PHP.
First, HipHop doesn't support create_function, which is used in the example.
Second, feature mismatch between Ruby and PHP will make efficient compilation quite hard and most likely be far from optimal. The languages doesn't seem to be very easily optimizable either.
HipHop isn't a silver bullet either: sometimes it seems to be faster than cached PHP bytecode, but not always.
His evidence from the author of Redis is not accurate - chronologically speaking Salvatore jumped to the other side of the fence to OS X more recently than two years ago on 8/27/2010.
He stated in his interview for usesthis.com that:
"In the past my desktop was running Linux as well, I used fvwm2, for more than 10 years, with this minimalistic setup. Now I miss it a bit… but switched to Mac OS as it delivers a much better “just works” experience for me, every time I want to do Skype, print a document, or alike."
Etsy really has the potential to become a major player in the micro-vendor market if it can take design considerations seriously - it may be at the vanguard of the industry at the moment but without actual design consideration for the future may be exactly the problem. I sometimes frequent the site and get the craigslist-this-will-probably-stay-the-same-forever feeling.
We are currently working on a new version of our Checkout product[0] and would love feedback. We are working on making the simplest drop-in integration to get up and running on Stripe, and we support Stripe Billing! Send me any thoughts you have (matt at stripe).
[0] https://stripe.com/docs/payments/checkout