blandinw
Joined 16 years ago
Karma
481
Submissions
36
Member since
Sep 23
Recent submissions
Comment · 7 years ago
Comment · 8 years ago
Passive-aggressiveness implies avoiding direct conflict. The author of this post refers to Acton not speaking up or making a good argument one way or the other, letting things evolve while resisting passively.
Also, the author is being very direct about what he thinks of Acton's behavior, he's not being passive-aggressive.
Comment · 9 years ago
You can read more on Reddit: https://www.reddit.com/r/haskell/comments/68obk4/open_sourci...
Comment · 9 years ago
(disclaimer: I work on Duckling)
I don't know of any benchmarks. HeidelTime and SUTime are two solid projects... although the rule files [0][1] are a bit scary if you ask me :-).
Quick thoughts:
- SUTime relies on TokensRegex [2] which is similar to how Duckling parses sentences at a high-level
- SUTime seems to only provide English rules
- I don't know of any production use cases of either
[0] https://github.com/stanfordnlp/CoreNLP/tree/master/src/edu/s...
[1] https://github.com/HeidelTime/heideltime/blob/master/resourc...
Comment · 10 years ago
No, it was rushed because F8 was getting close, we're a small team and we had ambitious goals in terms of features!
We had planned to release the Bot Engine at F8 long before MSFT's announcement. If you ask me, F8 might have affected their timing more than the other way around ;-)
Comment · 10 years ago
The team loves it. We're shipping features quickly and it integrates nicely with all the FB infrastructure (via Java). And of course, once you taste REPL-driven development.. you cannot go back :-)
Comment · 10 years ago
We're actually working on it :-)
The F8 rush took us a bit by surprise... Shipping soon!
http://imgur.com/hjswrHT
Comment · 10 years ago
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 :-)
Comment · 10 years ago
Bot Engine is not tied to the Facebook platform.
It exposes an HTTPS API that you can use from anywhere. Slack, the command-line, Messenger, a VR app, etc.
We don't make assumptions on your platform.
Comment · 10 years ago
(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.
TL;DR Haskell made more sense for us to scale with the number of requests (existing FB infra) as well as the number of engineers working on the project (type checking, etc).