https://news.ycombinator.com/item?id=4031699
That said, Aseem is very sharp. Nice to see this come up for discussion again.
192 karma · joined October 13, 2011
https://news.ycombinator.com/item?id=4031699
That said, Aseem is very sharp. Nice to see this come up for discussion again.
tl;dr:
In conclusion, in 1892 an important precursor of this family of expressions was published. The author was W. H. Davenport Adams, and his words may have influenced the version that T. H. Eliot published in 1920.
As it turns out, we're announcing our node.js SDK plans (with support) today:
If you want me to give you money, I'd like to see progress (and provide feedback) along the way, not just wait for the v1.0 release.
So in this case, it seems like you're using "Free and Open" as a label to get interest, but you're not really that keen on actually being open.
By making features an in-app purchase, they effectively monetize users going from version 1 to version 2, and so on. If you used the up-front payment model, new versions of the app would have to be a different app to continually monetize it, which would have a number of it's own problems.
If you're a high level eBay user, it's a fantastic place to move goods, but god forbid someone new signs up to buy or sell something. Just like what it must be like to sign up and play World of Warcraft for the first time.
If you highlight and copy in Chrome, you can paste straight into Clipboard, without having to do anything other than have the page open. It's by far my favorite new feature, and is worth pointing out.
The reality is that if someone wants your car they're going to get it.
Why get rid of an awesome convenience feature for the risk of something that is a) unlikely and b) won't cost you anything (absent a small deductible) if it does happen?
Services is where the logic of your application should live, and services should be HTTP (or any protocol) agnostic. They should only speak in models and native types, and should abstract all of your logic away from your controllers and models.
This leaves the controllers as a thin http handling layer that parses inputs and then lets the service handle the work.
The response from the service is then transformed appropriately (JSON, HTML, etc) and sent back to the caller.
Just my $0.02
That said, we haven't put the chrome extension in the webstore yet because we haven't yet opened up the service for public signup. As soon as we do it'll be in the chrome store.
Regarding the welcome email and the confirmation email, we saw a hacker news post that shared we'd have better success when the confirmation email had a clear and actionable subject. http://clipboard.com/clip/LQiJMrYD7dhXX8DWhgOoKa8A2PHm_0fHaw...
When you're doing hundreds of thousands of dollars (or more for you big guys) in credit card transactions, eating 1% just for a friendly API is a huge turnoff.
Please Stripe, prove me wrong and provide an external merchant account option!