[johnmarcus]

i wish my company was using Go for it's SOA instead of node.js. so much less overhead to run that neatly compiled binary than the dependency hell which is node.js. probably because node.js is hardly a language and almost every basic function needs to be imported from some third party, which also feels not so safe, as a sys admin. go is also easy to use.

[masom]

> almost every basic function needs to be imported from some third party, which also feels not so safe, as a sys admin

Go (and most languages) also supports importing a lot of packages from third-parties. Just pin your dependencies to specific known versions and do hash verifications.

[LunaSea]

At least Node.js has a built in package manager and not Github link hell like Go.

[notheguyouthink]

Fwiw, Go has an official package manager in development. Granted, they'll still be using repos rather than a central host.

[bpicolo]

npm isn't a built-in package manager. It's commonly packaged alongside node, sure.

[LunaSea]

It's separate to the language but there is actually an NPM version inside the Node.js repository if you build from source.

[bigdubs]

we use `govendor` to inline dependencies in tree; removes npm as a critical path when deploying, also means we can review dependency code changes like normal code changes.

[Bombthecat]

There is no soap library in go.

Or at least it is so basic, that it is useless (at leat I couldn't find any)

If you are a bank (or any old firm) . You need soap.

A lot.