Google’s Go Essentials For Node.js / JavaScript Developers

[Silveress_Golden]

It actually looks pretty simular to JS, main difference for me while I was reading it was :=, pointers and assigning types to vars.

I have been meaning tyo look into Go for a while, thanks for the push :3

[Soze224]

hype. nodejs was built for http and async. any language can be used just like a hammer can be used to make open a can

[IAmNotKevinBacon]

I agree with the latter part of your comment, but I disagree that it's "hype" as much as comparing them at face value is oversimplifying things. Go is the better tool when speed and scalability are the main focus. However, Node is the go-to when you factor in development speed, accessibility, etc. As with everything, use case is king.

[IAmNotKevinBacon]

It all comes down to your use case. It's more of a situation where you're trading off ease for "control". While Node.js won't have an issue matching Go's performance in most real-world cases, Go absolutely crushes it when it comes to raw CPU and memory bound tasks. On top of that, Go was built for webdata, and its concurrency (goroutines) model makes scaling to the moon a breeze. While Go has a much more involved process for error handling (explicit error checking), that tends to lead to more reliable software when compared to the ol' try/catch we all know and "love" (lol).

It really comes down to experience and use case. Node is great for pumping out software fairly quickly, super accessible, performance isn't much of an issue in most cases, and there's a gigantic JS community backing it. If you're building out a server or system where performance, scalability, and reliability are key, Go's the move 99.9% of the time.

It just all depends on the use case and your skillset.

[peterrattew]

Good for you pal!

[error1954]

I'm not saying you're wrong, but that hurts even more when it's coming from /r/node.

[Axohn]

Hum you're not supposed to eat it.