axw
Filebeat: https://www.elastic.co/guide/en/beats/filebeat/current/elast... (You can incorporate variables in the destination index; variables may refer to labels and other fields.)
Ingest node: https://www.elastic.co/guide/en/elasticsearch/reference/curr... (search for "_index")
We use this in the development of Juju. We also have a bot that creates Review Board reviews from GitHub PRs, and updates the diffs when the PR is updated.
http://blog.awilkins.id.au/2012/12/go-in-browser-llgo-does-p...
Sadly I don't have a lot of time, so progress is quite slow. The PNaCl support isn't working at all at the moment, as I'm going through a fairly major refactoring to make things a bit more solid.
Fair enough. I wrote that post for a much smaller audience (namely, people already following the llgo project), and certainly didn't expect it to be posted to HN. You're right of course, I should always consider people unfamiliar with the project stumbling across my posts.
I don't know the first thing about iOS development, so can't comment there.
If you'd like to work on a feature, please let us know on the llgo-dev group: https://groups.google.com/forum/?fromgroups#!forum/llgo-dev
Please be aware that this is still fairly rough around the edges, and I'm new to this game (compilers/language implementation, beyond toys).
Thanks!
TL;DR: functions are now represented as (function pointer, pointer to a context structure), whereas before they were represented as a single function pointer.
Pushy is Python-based, not PERL-based, but otherwise it's similar what you/Matt describe. It never really made much ground, though I recently became aware that Ceph is using it in their ceph-deploy deployment program.