blandinw

I touched on that on Reddit: https://www.reddit.com/r/Clojure/comments/68r4lz/one_of_face...

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).

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.

You can read more on Reddit: https://www.reddit.com/r/haskell/comments/68obk4/open_sourci...

(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...

[2] https://nlp.stanford.edu/pubs/tokensregex-tr-2014.pdf

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 ;-)

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 :-)

We're actually working on it :-) The F8 rush took us a bit by surprise... Shipping soon! http://imgur.com/hjswrHT

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 :-)

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.

https://wit.ai/docs/http/20160330#converse-link

(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.

He's the founder of Sandwich Videos, I believe: http://sandwichvideo.com/people/. They make pretty cool stuff :)

It's a mistake French (Latin?) speakers (myself included) often make: https://translate.google.com/m/translate#fr/en/infirmer

Fixed, thanks!

Fixed, thanks.

You're spot on. The next version of Duckling will return the list of assumptions made, as well as a list of alternate results. Applications will also be able to give assumptions as input (past vs. future, etc.).

cf. my answer to another comment. Even though the demo website expects the whole input to be a time expression, Duckling -- used as a library -- actually detects substrings inside a larger block of text.

EDIT regarding 6pm vs 6am, applications will have control over the assumptions made by the system. See https://news.ycombinator.com/item?id=8397113

Even though the demo website expects the whole input to be a time expression, Duckling actually detects substrings inside a larger block of text.

We've mostly used it on short sentences, but it should work on larger inputs, like articles. I'd recommend splitting very large inputs into sentences though.

The docs were outdated indeed, we fixed this, thanks!

This: https://bugzilla.mozilla.org/show_bug.cgi?id=957724

I totally understand what you mean.

But as a bootstrapped startup, we have to make tradeoffs as our budget is limited. We have to accept invitations gradually today to keep our servers alive. We should be able to accept everybody within a few days at most. Sorry for the inconvenience.

Haha, sorry about that.. I guess we are better at Clojure than Angular.js!

Working on a fix now.

Hi Tony,

After reading http://octodex.github.com/faq.html, we thought it was okay to put this image given that we advertise and reference GitHub a lot, we heavily integrate with it and we love Octocat!

Do you think we should remove it?

Thanks!

Regarding Opera, it has been tested and everything should work as expected!

Can you email me your GitHub username at [email protected] to make sure we got your request? Thanks!