> In Node, the standard library is effectively non-existent, so Node devs get trained and acclimatised to dependencies.
Have you ever actually taken a look at it? https://nodejs.org/api/index.html
> In Golang, dependencies are minimised. Everyone tries to stick to the standard library as much as possible. Because the standard library is so good, for most projects this is perfectly reasonable.
Meh. The Python stdlib has been considered "good" for a long time[0], but the last few years people commonly reach out for external dependencies.
It's not because the stdlib has gotten less good (the opposite), it's because the experience of publishing and using external dependencies has significantly improved.
> I'd say the first thing every Node dev should know when learning Go is that they don't need a dependency manager.
They do, they just don't have one. Which is why people tend not to bring in external dependencies: bringing in external dependencies in Go is a traumatic experience, much as it used to be in Python a few years back.
[0] in fact this exact same argument was relatively common in the mid-to-late aughts, Java developers dipping their toes into Python would complain about the state of dependency management and get told that the stdlib is so good you don't need dependency management, the stdlib is almost all you need and there's no need for advanced dependency management for just one or two dependencies…