Hacker News Reader

Comment by rartichoke | Hacker News Reader

No, they have much different ways of dealing with concurrency. Deployment is a solved problem in most modern languages.

I think you may have misunderstood my post?

I also spent a pretty decent amount of time performing real world benchmarks for both languages by writing applications in both and then ran various performance metrics. Performance for general web apps with real world data goes back and forth depending on what you're doing.

My point was Go doesn't offer nearly enough pros for it to worth switching to.

View on HN

If by "solved problem" you mean "if you accept the problem of keeping an up-to-date deployment environment on every machine with up-to-date patches", compared with "build this binary copy it over and run it", yes, Node and Golang deployment is comparable.

I think you're mostly just handwaving.

It is a solved problem. You can't just copy over a folder (or file) and call it a day but it doesn't take that much to get Node deployed by simply typing 1 command on 1 machine and this is the same thing you would end up doing for Go too.

If you ever dealt with deploying to more than 1 machine you would realize that doing it by hand is a pretty crazy idea. The first thing you would do is create a solution that allows pretty much hands free deployment, and those solutions exist for every modern language. Heck, it's one of the first things I did as a developer even while deploying to 1 machine.

> this is the same thing you would end up doing for Go too.

No, you'd just need to copy over one binary. Go programs compile to a system binary.

Ok, so you're going to be scp'ing your binary over manually every time? Do you manually do your other build tasks too?

No, you would have a build script that minifies/concats assets, runs tests, maybe generate docs, then finally deploy using whatever method you happen to be using if everything passes.

This might be a git deploy, or scping files over to some server.

In either case you're never copying 1 file over because that is abstracted away from you by your build script. In return you type 1 command and let your build script do the dirty work for you.

Typing this one command is the same if you're using Go or Node or any other modern language. It doesn't really matter that I have to add a few extra commands to my build script because these are things I only have to do once.

> You can't just copy over a folder (or file) and call it a day ...

Yes, yes you can.

Reply on news.ycombinator.com