- python -> c++ is one less layer of complexity to reason about than python -> c -> go - the go runtime is great for developer ergonomics, but is going to cost more flops than equivalent code in c++ because of features like garbage collection. additionally the concurrent features of go are great but concurrent ML backends will probably be used a lot more than they are read + written, so probably a fair tradeoff to sacrifice readability for performance here. On Sunday, April 14, 2024 at 8:15:51 AM UTC-4 envee wrote:
> After reading briefly about ML and how Python is used as a "veneer" for > C++ code, I was wondering why Go is not used as the backend, given it's > excellent concurrency support and ease of use. > Basically, I was thinking if the backend is written as a shared object in > Go, and then used in Python using ctypes. > I have seen a huge number of libraries on the awesome-go website, but > don't know if they have Python bindings. > Any views ? > What really is a limitation which does not encourage developers to prefer > Go over C++ as the ML backend ? > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/dc8d6282-d1cf-43db-a0ee-a1347e345638n%40googlegroups.com.
