>>105713699> been buckbroken by very shitty languagesSo, i just recently adopted go from working with C++ and C for 30 years.
It’s not bad. In this case, though, I used it for a few reasons:
compatibility back to Windows XP (with go v1.20)
I also need modern crypto.
It’s easy to deploy since it’s one big-ass binary.
Runtime doesn’t bother me (in this situation), and it’s not performance critical.
It’s C-like so no problems there. Going back to C# from C was objectively worse.
Normally I was shitting on go, because the “one big binary” thing was because they couldn’t figure out (dynamic) linking.. so they spun it into an asset, but for me with generations of DLL hell, it *is* an asset.