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

The compilation time is slower, not the resulting compiled binary.

> On average the programs in the Go 1 benchmark suite run a few percent faster in Go 1.5 than they did in Go 1.4, while as mentioned above the garbage collector's pauses are dramatically shorter, and almost always under 10 milliseconds.



I'm referring to compilation speed. In Python and Ruby, for example, there is no compile stage. This makes them attractive for rapid iteration.


Meh, most people will never notice it, and if for someone is an issue, you can continue to develop using 1.4 locally until 1.6 comes in 6 months.


There is a compilation-to-bytecode stage + lots of file look ups during start up of the Python interpreter and during every module import.


Python caches the bytecode in .pyc files, so the compilation happens only the first time you import a module. In a typical Python start-up only the main source file is byte-compiled.




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

Search: