avlapp

Thanks for your comment. Maybe you could keep this question open, so others might chime in. Label it as question for instance.

While others told me on IRC that Go wasn't well suited, some interesting insights where shared recently by siXy in #go-nuts: For audio go's GC is good enough, if you...

My current take is that it might not be a bug in scgolang/osc. Using multiple workers is possibly just making the order of delivery of the packages less reliable. UDP...

I'm fairly new to Go and pointers. I found this: https://youtu.be/29LLRKIL_TI?t=888 So I think your point is valid and on top of that, pointers are not concurrency safe.

Or should I make another socket file for the client? That seems to work, I'm able to receive a 'pong'. ``` addr, err = net.ResolveUnixAddr("unixgram", mySocket) if err != nil...

Interesting thoughts. See also: https://www.cs.cmu.edu/~rbd/papers/o2-icmc-2022.pdf At the moment there isn't a golang osc library with implemented/ supported TCP support it seems.

Ok, good to know you're still around at least. @briansorahan