233 karma · joined February 27, 2013
From the perspective of a new startup, Plaid also has a much more modern API and treats documentation as a much higher priority than most of their competitors - you can get up and running in an afternoon, which is absolutely not the case for every provider in the space.
Plaid also had much better support, at least in the early days - level 1 support was a native English speaker with deep technical knowledge of the product, level 2 support was a founder of the company.
EDIT: It's actually worse than that, see comment from erichurkman below.
> You might have noticed several unusual things about how I discuss Autism. I’ve capitalized Autism, and I have not once used the word “disorder” or “syndrome” in tandem with it. I also say Autistic, rather than “person with autism” -- the term Autism Speaks, an organization despised by most Autistics and many of their parents, would prefer you to use.
To be clear, Sliced is open only to accredited investors and has a minimum investment of $20,000.
And here's the best part: http://ftalphaville.ft.com/files/2014/08/Screen-shot-2014-08...
Historically, some brands did create full Facebook accounts, but Facebook now discourages that and as far as I know most brands are using Pages now. For a while Zuck's dog, Beast, was a notable exception (he had a Facebook account long after that was discouraged) but it looks like he's just got a Page now.
(I used to work at Facebook.)
Don't worry about complex package management systems, or what environment a consumer of your program might have.
Just give them a copy of your environment: it will always work in the future."
I'm not convinced that a virtual machine snapshot is an adequate replacement for wrestling with a package manager. If all you distribute is a VM image, then:
- Users can't easily run your software without provisioning an entire virtual server and, as far as I can tell, giving Terminal money and their email address.
- Without active maintenance on your part, the other software on the image will get out of date. Security holes will be discovered in the versions of nginx and openssl that your image uses. Have you ever tried to upgrade a Linux box that hasn't been touched in a few years to the latest version? After a few years, every potential user of your software will have to go through that first.
- If Terminal goes out of business or pivots, your image will no longer work (I think?).
- Your software will not fit naturally into your users' deployment environments. It will not by default show up in their administration tools, know about their VPNs, integrate with their logging infrastructure, or appear on their graphs.
I think this makes a lot of sense as a low-friction way to distribute software, but if you're writing code that people will care about in a few years it shouldn't be the only way.