Getting it to a state, even the minimal one, where it's ready for launch has taken slightly longer than expected. :(
Right now I'm reworking the API a little bit. I realized that the means of specifying new vocabulary for it was not at all friendly for coders who don't have lots of type theory background. I have a new way of doing this that I think will work, and it'll be up hopefully within a few weeks.
The demo is nice. That said, SQL Server had a language processing plugin which could translate normal text to a SQL query, this was back in the days.
Which languages do you support?
I don't know about SQL's natural language support, so I won't comment.
As for languages, the technology is independent of particular languages, so you can in principle add modules for, say, core Mandarin vocabulary, and then write your apps for Mandarin. I only speak English, however, so I can only add core vocab for that. :\
There are also interesting possibilities of cross-pollinating apps, so that as more developers use LE, its out-of-the-box capabilities grow. There's no reason, for instance, that developers should be re-inventing the wheel each time someone builds an app or a robot or whatever. Imagine if every human was born with the cumulative knowledge and skills of all previous humans. Now imagine you can do that with AI.
