["interactive islands"]: https://fresh.deno.dev/docs/concepts/islands
227 karma · joined March 2, 2014
["interactive islands"]: https://fresh.deno.dev/docs/concepts/islands
- If something is not documented well, it is probably tested well. If you can find the tests that cover it, you can usually get a good idea of how it works. - There is no multithreading. I had to fake it by breaking up my loops with setTimeouts.
There is an IRC channel if you need a place to go for help. Also, feel free to PM.
Much thanks to @iffy for writing the first pass.
It uses voxforge's sample vocabulary, so you'll need to say things like "Dial 1 2 3" or "Call Kenneth McDougall" for it to understand you, but the vocabulary is easily swapped out for your own projects, as explained in the README.
I'll be sure to include them soon - it's probably just a few more lines of code, so you can expect them in the onrecognition function this afternoon.
> VoxForge was set up to collect transcribed speech for use with Free and Open Source Speech Recognition Engines (on Linux, Windows and Mac).
VoxForge's sample grammar is provided as a default, in its own folder [2]. It would be nice to get a high-quality acoustic model, as voxforge's is not that comprehensive yet, but I couldn't find anything with the right licensing and zero cost. If anyone knows of one, I'd love to hear about it.
[1] http://www.voxforge.org/ [2] https://github.com/zzmp/juliusjs/tree/master/dist/voxforge
I also came across PocketSphinx, which has been around a little longer - that may have some users in the wild already, and I wouldn't be surprised if it was used for navigation somewhere.
[PocketSphinx] https://github.com/syl22-00/pocketsphinx.js/
"It would then be down to a judge to decide if the parody is funny."
Can't wait to see that lawsuit...
How easy did you find it to work with NLTK?
Did you have a lot of NL experience before this project? Do you think something like NLTK would be easy to pick up?
We also have session, which works on a HashMap under an Arc, although it isolates the mutable data to a session, instead of sharing it across isolated requests.
The 200 is being served as the default of `rust-http`. Static will never serve a 404 - it will only defer to the next middleware, and the docs server is overly simple, so it just goes to default.
Unfortunately, I'm not sure if anything in Rust should be considered `production-ready` yet, and I haven't worked with any ORM wrappers in Rust (yet).
I think we could get tests 1 and 6, if you'd be interested. I'll try to get to those soon.