Conversation
Outstanding! How have the go bindings been treating you? Feel like wins from sharing defeat complexity and overhead?
1
1
2
Yeah, I saw that. Definitely cuts down on FFI noise, though of course the infra is heavy. Happy you went this way?
1
2
1
It's worth noting we picked this path since we already had a msgpack-RPC interface to the core service
1
Gotcha. What was the original client of that msgpack service? Good to hear from you too Max!
1
1
Gotcha, makes sense. Curious why you didn’t go with a C/C++ library and FFI—preferred Go for safety / dev happiness?
3
Exactly. Had enough fun in previous life trying to get C++ to work. One of Go's finest attributes is that the
1
Replying to
Makes sense. You certainly don’t have to convince me of C++’s comparative incoherence. :)
Replying to
OTOH, my biggest complaint about Go is that often I don't want multiprocess parallelism, I just want network...
Replying to
concurrency. In Go, can't have one without the other, so now you're locking the setting of `this.flag = true`..
1
Replying to
or using channels. If using channels, you're going to have the same concurrency bugs you'd have with locks...