I will take sometimes-tedious boilerplate over many-many-layered abstractions. You can write any language any which way, but some languages just have a culture

I will take sometimes-tedious boilerplate over many-many-layered abstractions. You can write any language any which way, but some languages just have a culture of boilerplate vs abstractions. The most popular Python and Java libraries seem to love endless layers of indirection, and when it doesn't fit exactly what you need, you bang your head against the wall monkeypatching it to make it work since your whole app is already written in X mega library. Go culture seems to be quite a bit more boilerplate-y and uses smaller more composable libraries. It's just refreshing. Really I just need to buckle down on Rust, but I think it's a fair bet that teams and shops that bring in a lot of young programmers and want to ramp them up fast may cringe a bit at the learning curve of Rust. That's why for now in terms of a bet on employability, I am prioritizing experience with Go.