To boldly go where Node man has gone before

Post by _ak » Wed, May 16, 2012, 9:27 PM UTC

kbd wrote: post #4

jgrahamc wrote: post #3

Earlier quoted context omitted.

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.

Post by _ak » Wed, May 16, 2012, 9:31 PM UTC

chc wrote: post #9

kbd wrote: post #2

So 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.

    type UploadProgress struct {
        Progress int `json:"progress"`
    }

    //...
    // variable progress is of type Progress
    if json_data, err := json.Marshal(progress); err == nil {
        w.Header().Set("Content-Type", "application/json")
        w.Write(json_data)
    }

Post by paufernandez » Wed, May 16, 2012, 9:44 PM UTC

KaoruAoiShiho wrote: post #54

paufernandez wrote: post #34

Earlier quoted context omitted.

It works very well for me. If I want someone to install a Go program I've developed, in Ubuntu 12.04 they can just: $ sudo apt-get install golang $ go get github.com/pauek/garzon/grz That's it, and it takes a few seconds.

How's that any faster than npm install express Not only do npm handle versioning for you, you also don't have to remember the host or username. Obviously Go is a younger community, and could make a package manager some day, but I'm puzzled by how you're comparing this positively with npm.

Post by baudehlo » Wed, May 16, 2012, 9:59 PM UTC

KaoruAoiShiho wrote: post #55

paufernandez wrote: post #34

Earlier quoted context omitted.

It works very well for me. If I want someone to install a Go program I've developed, in Ubuntu 12.04 they can just: $ sudo apt-get install golang $ go get github.com/pauek/garzon/grz That's it, and it takes a few seconds.

Oh I get it, you're talking about from a package developer's standpoint. Not having to register your package with a central directory does save a bit of time for you I guess. But when installing packages, I have to say, npm is fantastic.

Post by taligent » Wed, May 16, 2012, 10:03 PM UTC

moocow01 wrote: post #58

If there is one thing I've learned its to ignore benchmark tests on relatively established technologies. You'll drive yourself into the looney bin if you hop from one thing to the next based on these comparisons that inevitably popup every month or so. If you enjoy programming in JS with Node use it - if you enjoy programming with Go use it. Your enjoyment will far outweigh performance differences that will be minor…