To boldly go where Node man has gone before
blog.jgc.org
To boldly go where Node man has gone before
1–10 of 124 posts
Re: To boldly go where Node man has gone before
#2So does Go's net/http module really provide basically exactly the same programming model as Node? If so, why use Node?
One thing the author didn't mention is that Go will use multiple cores in this example, whereas Node is single-threaded. Right?
Re: To boldly go where Node man has gone before
#3So does Go's net/http module really provide basically exactly the same programming model as Node? If so, why use Node? One thing the author didn't mention is that Go will use multiple cores in this example, whereas Node is single-threaded. Right?
It's true that Go can use multiple cores, but I was doing these tests in a Ubuntu VM that was restricted to using a single core so that Go's inherent 'multicore' advantage was dialed down. I'll add a note to the post.
Re: To boldly go where Node man has gone before
#4So does Go's net/http module really provide basically exactly the same programming model as Node? If so, why use Node? One thing the author didn't mention is that Go will use multiple cores in this example, whereas Node is single-threaded. Right?
It's true that Go can use multiple cores, but I was doing these tests in a Ubuntu VM that was restricted to using a single core so that Go's inherent 'multicore' advantage was dialed down. I'll add a note to the post.
That's a(nother) pretty big real-world advantage for Go then, no? I know the solution for Node is to just run one instance per-core, but it's automatic with Go.
I'd love to see a second set of benchmarks of the same code on multiple cores.
Re: To boldly go where Node man has gone before
#5My favourite thing about posts like these is the little comparison snippets between a framework I already know (Node) and a language I want to learn (Go). This is very educational, and the benchmarks are the cherry on top. Thank you.
Re: To boldly go where Node man has gone before
#6I'm sure the reason why users pick node is probably similar reasons why one picks ruby/python -- it's not for the speed.
The language of the web is javascript. Until web browsers allow Go as the embeddable language, node will remain useful. I seriously doubt people would pick Go over node because of a micro-benchmark.
Re: To boldly go where Node man has gone before
#7Choosing Node.JS isn't just a performance / scaling decision for me -- one of the main draws to Node is the huge community and wealth of awesome modules. Socket.io, Now.js, cradle, redis, and dozens of other modules abstract away the tedious work and let me build functionality _really_ fast.
Go is really promising but it won't win over the majority of casual developers until there's a community around it. I might as well write a webserver in C if I'm only concerned with performance
Re: To boldly go where Node man has gone before
#8I'm sure the reason why users pick node is probably similar reasons why one picks ruby/python -- it's not for the speed. The language of the web is javascript. Until web browsers allow Go as the embeddable language, node will remain useful. I seriously doubt people would pick Go over node because of a micro-benchmark.
> The language of the web is javascript. Until web browsers allow Go as the embeddable language, node will remain useful.
Do people really get that much code re-use between client and server that using Javascript on the server provides a large benefit?
Re: To boldly go where Node man has gone before
#9So does Go's net/http module really provide basically exactly the same programming model as Node? If so, why use Node? One thing the author didn't mention is that Go will use multiple cores in this example, whereas Node is single-threaded. Right?
> So does Go's net/http module really provide basically exactly the same programming model as Node? If so, why use Node?
Well, for starters, Go is much more awkward for working with JSON than JS is (which is to be expected since JSON is literally a subset of JavaScript). More importantly, Go lacks the ridiculously vibrant ecosystem for Web development that Node has — no NPM, no Connect, no Jade, no Stylus, etc.
Re: To boldly go where Node man has gone before
#10Choosing Node.JS isn't just a performance / scaling decision for me -- one of the main draws to Node is the huge community and wealth of awesome modules. Socket.io, Now.js, cradle, redis, and dozens of other modules abstract away the tedious work and let me build functionality _really_ fast. Go is really promising but it won't win over the majority of casual developers until there's a community around it. I might as…
As we are commenting here, the community is assembling by the minute... Go allows you to import "github.com/user/package" and will download and compile the code, so creating a new project is even easier than with node, no need to "npm install ..." first.
For a taste of what's out there, see: http://go.pkgdoc.org/index.