It's funny, when using C++ or Rust, Go feels like my version of Python/Javascript/Etc. There's something very appealing of it to me.. it's the NodeJS of the Typ

It's funny, when using C++ or Rust, Go feels like my version of Python/Javascript/Etc. There's something very appealing of it to me.. it's the NodeJS of the Typed world to me, and i love it for that. Granted, i'm trying to switch my codebases to Rust, but still - i can't imagine going back to Node/Python/etc. But to each their own, i'm not foolish enought to say i'm "right". With that said though, i have a hard time understanding complaints like: > if err != nil { gets old even faster. I may be biased, because my time in frontend JS land, but i love checking errors every time. It's a language feature to me. Ignoring errors and expecting something else to care and catch/handle them is just.. worrying to me. Likewise, try .. stuff .. catch .. stuff .. Gets far older to me than `if err != nil {`. But that's just me i suppose.