Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's chickens*t to down vote my comment, when you could argue a fact, or explain something to me that I don't understand.

My question isn't silly. I just now wrote two short programs, one in Go and one Javascript, to run a vector multiply and add on two length 1000 vectors, a million times. The JS program is faster.

Result (in seconds):

  $ node vmadd.js
    0.984
  $ go run vmadd.go 
    1.141044662
JS code: https://gist.github.com/hwinkler/62c9da0d9f2d8c7981b0

Go code: https://gist.github.com/hwinkler/d234bb62b2c5fa081a50



Go run first compiles the code and builds an executable. You are mostly benchmarking for both systems the compilation time. Building an executable in Go takes most of a second. A significant benchmark would check the run times.


No, if you examine the code, you'll see the timer times only the accumulated execution time for the loop. The code has been compiled. See below to eliminate doubt -- I used go build and got similar numbers.


Exactly. Build it and then benchmark the binary. Nobody uses `go run` in production.


  $ go build vmadd.go
  $ ./vmadd
  1.106074715
This is a 2013 Core i7 15" MBP


I'd rather be right, than have karma.


This is obviously a highly scientific experiment! I get the exact opposite results!


Even if you got the opposite numbers, it shows that the js code is nearly as fast as the go code.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: