It’s hard to answer without specifics but languages shouldn’t require you to determine whether it’s safe to use an api in an async context or whether it will hang your app. I imagine some of the sharp edges you might have run into are because go has real parallelism and you have to address data sharing.
This is fantastic progress for CPython. I had almost given up hope that CPython would overcome the GIL after first hitting its limitations over 10 years ago.
That being said I strongly believe that because of the sharp edges on async style code vs proper co-routine-based user threads like go-routines and Java virtual threads Python is still far behind optimal parallelism patterns.
I did this for several years before but it was a constant maintenance burden because as third party services were integrated or removed over time. Eventually as AWS and third-party CDN usage grew routing by subnet was just not feasible.
I built a program in Go to defeat GeoIP lock-outs for my home network.
It runs on our home router and functions as the primary DNS server. If the record name matches a regex the DNS request is forwarded over a VPN to a DNS server in the target country. Any other requests are forwarded to my ISP’s DNS. If the response is a CNAME then the A record name is cached so that follow-up requests are also forwarded over the VPN.
Before returning the IPs in the foreign DNS response /32 routes for the IPs are added to send any home network traffic for them over the VPN.
This means that any client on our home network can transparently access GeoIP locked sites. It’s worked for around 8 years with no modifications.