(cofounder of Wit.ai here) Thanks for your kind words :)
I understand your concerns, here is my take.
X as a service allows you to get X with a lot less efforts.
It allows you to understand the problem and your needs by getting started quickly. Over time, if X as a service saved you enough time and you become successful, you can choose to develop an expertise in X and cut the dependency.
Wit is also about building a community of developers and advancing the state of the art of NLP in apps. Once the bot engine matures a bit, we'll be focusing again on the community aspect of Wit and hopefully advance the field enough so that efforts like the standardization you mentioned are started.
> X as a service allows you to get X with a lot less efforts.
I think it's more accurate to say that it allows you to borrow X. It's very true that it helps to bootstrap your own product and eventually if things work out you can bring X in-house.
My worry about everything-as-a-service is that until that point, each different service that you use is an another vulnerability to your product. This goes double for specialized services like AI, where unless you already have experts in that field, you're unlikely to have the expertise to replicate the service in-house. (Although by that same token, in this case without the service you couldn't provide your product anyway.)
There's little risk of depending on external services if you use multiple that provide the same type of service hidden behind an abstraction layer and can remove one of the vendors from the mix with the press of a key.
That mitigates the risk of depending on services, but it introduces a huge new risk by committing development time to a feature that provides no value to the user and potentially, if the providers last, no value to the business either.
Any startup founder who follows this strategy is concentrating on the wrong thing. Pick the provider who's most likely to last and build against their service. That way you are more likely to fail than they are.
You're conflating "using an external product" with "using an external service". The third option is self-hosting a third-party product, which gives you the best of both worlds (reduced development cost and time, reduced risk due to continued reliance on third party).
Could you explain why it is in your best interest to do so? Unless your community-based efforts are focused on "built on Wit", you would be actively lowering the bar to entry.
From a company standpoint, the commoditization of the GP's comment is directly counter to your incentives as a business.
Not sure I correctly understand your question, but I'll give it a shot.
Today, Wit offers many advantages out-of-the-box so you don't have to setup your own solution.
As NLP gets more commoditized (e.g. through open-source, open datasets), Wit will have to provide even more value than today to stay relevant. Value can be ease of use, accuracy, etc. That's how the field makes progress.
Regarding best interest, if you mean FB's best interest, FB wants more intelligent bots in Messenger, VR, etc. It makes sense to provide the tools to do so. Opening these tools also helps make them better (why is FB open-sourcing React for example?)
If you mean the Wit team's best interest, we're always happy to provide better tools to developers and innovate in AI / UX. That's why we started Wit after all :-)
X as a service allows you to get X with a lot less efforts. It allows you to understand the problem and your needs by getting started quickly. Over time, if X as a service saved you enough time and you become successful, you can choose to develop an expertise in X and cut the dependency.
Wit is also about building a community of developers and advancing the state of the art of NLP in apps. Once the bot engine matures a bit, we'll be focusing again on the community aspect of Wit and hopefully advance the field enough so that efforts like the standardization you mentioned are started.