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.
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 haven't even thought about that to be honest, but there's not currently anything that would preclude embedding code generated by llgo in a C program. This might change in the future, with the introduction of goroutine scheduler and segmented stacks.
I don't know the first thing about iOS development, so can't comment there.
TL;DR: functions are now represented as (function pointer, pointer to a context structure), whereas before they were represented as a single function pointer.
I haven't seen that before. Thanks, it brought a smile to my face. I made this a few years ago: https://github.com/axw/pushy
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.
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")