Hi team, I have a question that I hope can be answered. LiveKit uses Go as the server-side development language, and the core of the client SDK is built using

rust-sdks

. Regarding the

server-sdk-go

, this library is primarily for server-side interactions. Since WebRTC is P2P-based, I'm wondering if I can use the

server-sdk-go

library as the client SDK in the core layer? I don't fully understand the differences between the

rust-sdks

and the

server-sdk-go

. What I know is that media stream capture and platform-related features are likely implemented in Android or iOS layers, but I'm concerned about the differences between the

rust-sdks

used in the core layer and the

server-sdk-go

. As far as I know, both libraries may only expose the core WebRTC interfaces, but I wonder if there are significant differences. Regarding using Go and Rust for the core layer, I already understand that Rust performs better, has smaller package sizes, and provides better client-side support. If we ignore these factors, can I directly use the

server-sdk-go

to build a core layer like the

rust-sdks

? Apologies for the detailed question—this is based on the needs of our project. Our core layer is implemented in Go, but due to Go's runtime limitations, we cannot include two Go libraries simultaneously. So we are considering merging them into one SDK. However, we're unsure if the core capabilities of

server-sdk-go

(which is designed for the server side) can be used similarly to the Rust

rust-sdks

. We can add platform-specific features (e.g., Android and iOS), but we need to confirm whether this is feasible. Thank you very much!