Golang: Easy to get started, hard to master (worth it) - maturing and run by experienced if opinionated people. Node: Easy to get started, can let you get shit

Golang: Easy to get started, hard to master (worth it) - maturing and run by experienced if opinionated people. Node: Easy to get started, can let you get shit done. Easy to dig your own grave, problems sometimes come from left field. Honestly, writing golang makes me feel like I'm trying to revive Brutalism - it is blocky overbuilt and feels solid - it just doesn't feel "elegant", and you really don't want to cut corners. Node is more "fun" - but it just feels like I'm adding to a pile of hacks and checking that in - Node: I have been bitten by more than once - situations totally out of my control left me dead in the water. Golang, not so much. Lastly when I work in go, I can understand my dependencies and deal with them. Most of my node experience entails praying all the dependencies work and dealing with it if they don't or stop. Really the choice is yours because both WORK, but for me personally I would not want to work in node again. Honestly set them both up and figure out what one you like more - it should not be hard to write a basic sign up and log in micro service.