Eelco
@frankjoke the forked repo is already there. This PR originates from there. You can find the link below the title where it says [`eelcocramer:master`](https://github.com/eelcocramer/node-bluetooth) but I've also added it [here](https://github.com/eelcocramer/node-bluetooth)...
Well, I'm not going to publish it. But you can fork it and publish it yourself if you need it.
For the convenience of folks that use the javascript patterns used in @song940's module I've updated my PR to use the experimental C sources from my fix branch. So you...
I've added mangos to [an existing message benchmark](http://blog.jupo.org/2013/02/23/a-tale-of-two-queues/) that I stumbled upon. It compares benchmarks of python and golang messaging solution. For golang it compares zmq, redis and now mangos....
Thank you for the response and the solution pointers. I'll dig into this and post results back. I will remove the graph because it probably does not good reliable information.
Thanks for the extensive answer.
Any update on this? For a Go project probably the easiest thing would be to use something as [goreleaser](https://goreleaser.com) for the build and release process. Next to releasing binaries it...
I will take a look at your workflow to see if I can contribute to it.
I run into the same issue. @gp187 should that be added to the build dependencies script?
Maybe. But then the log level should be set to error as a default in non-interactive mode right?