This an API, jQuery autocomplete is a Javascript library. Typeflow is inteded for big amounts of strings to autocomplete. It lets you push a list of strings to the typeflow API and exposes an endpoint for querying it via an HTTP API. You can easily make it working with Twitter Typeahead or jQuery autocomplete leaving the computation of the suggestion to the API.
Thank you for letting me know. I don't have an iOS device handy to try but I'll investigate anyway to make it working on mobile as well. Should work on FF and Chrome desktop though. :)
The author must have been undergoing some bad moments so far. The post seems just the outcome of a more complex series of inputs. Most points are not valid from my own personal point of view but still may have been good points if written in a more objective way.
I don't think I'll put much effort in this project since this is barely a proof of concept but there's a couple of points I would like to dig if I ever find time:
1. How to reduce collections generations?
2. How to take advantage of the machine cores to execute the Map/Reduce operations?
As a little side node I'd personally rename main.go to core.go. Plus, I think there's room for splitting main.go into more little pieces to ease maintainability.
Despite being always interested in seeing benchmarks comparing new languages I don't feel like basing my choices on such benchmarks. From my experience it's usually a matter of how comprehensive is the ecosystem surrounding the language. Anyway, great article.
Tried EventMachine in the past but not with this particular use case. Actually my nginx+passenger configuration allowed for 12 workers, but I may have counted wrong the running instances at the time of the deadlock.
Anyway, what is interesting to me is trying to understand how actually Rails handles and releases MySQL connections. In fact, even with the timeout dance I implemented I didn't seem to succeed in releasing MySQL connections.