It is a matter of perspective. For my personal projects I decided some time ago that I would use javascript both frontend and backend. That was a world of pain,

It is a matter of perspective. For my personal projects I decided some time ago that I would use javascript both frontend and backend. That was a world of pain, mostly attributed to the lack of static typing, asynchronous nature implemented through callbacks, and the pain of choosing alternatives in the chaotic ecosystem. It was somewhat alleviated when I switched to Typescript, started to use async and await, and settled in some choices (Bootstrap, React, webpack...). But then I tried the golang. Yes, the lack of generics hurts a bit, but otherwise it is an absolute damn pleasure to use: static typing, reliable completion in IDEs, batteries included, more clarity in choice of modules. It just felt right. Granted, it is my multi-year background in C and C++. For me multi-threading and co-routines just feel more natural way of doing concurrency than callbacks and CPS.