Earlier quoted context omitted.
This is plain wrong, the main reason the compiler is fast according to the authors[1] is because it handles dependencies more sanely than C/C++. https://talks.golang.org/2012/splash.article
You're more than welcome to write C in the fashion that the go compiler enforces, and get much faster builds. Their compiler is young and immature relative to things like GCC and stating that it may be missing expensive optimization features is not "plain wrong".
Go 1.5 Beta
51–60 of 82 posts
Re: Go 1.5 Beta
#52Earlier quoted context omitted.
Fast builds is definitely a major feature. Go has attracted more Python developers than C++ developers. http://commandcenter.blogspot.it/2012/06/less-is-exponential... Go is great as a much faster Python, where speed matters. If Go compiles slow too much, it becomes less attractive.
How often do you compile a code versus run it? Particularly in cases where speed matters?
Re: Go 1.5 Beta
#53Re: Go 1.5 Beta
#54Can anybody clarify what is meant by " Generate machine descriptions from PDFs (or maybe XML).", " "Read in PDF, write out an assembler configuration"."? That sounds . . . ambitious. https://talks.golang.org/2015/gogo.slide#22
Re: Go 1.5 Beta
#55Re: Go 1.5 Beta
#56Earlier quoted context omitted.
I'm referring to compilation speed. In Python and Ruby, for example, there is no compile stage. This makes them attractive for rapid iteration.
There is a compilation-to-bytecode stage + lots of file look ups during start up of the Python interpreter and during every module import.
Re: Go 1.5 Beta
#57Really wish these HN links to download pages were HTTPS. Lots of people at Gophercon on untrustworthy conference wifi that probably wouldn't notice a MITM'd download page pointing to non-HTTPS binary downloads.
Work is ongoing to make golang.org be HTTPS only.
Re: Go 1.5 Beta
#58Well we can toss out Go as a suitable language for real-time applications such as video games and audio processing.
Re: Go 1.5 Beta
#59Re: Go 1.5 Beta
#60Can anybody clarify what is meant by " Generate machine descriptions from PDFs (or maybe XML).", " "Read in PDF, write out an assembler configuration"."? That sounds . . . ambitious. https://talks.golang.org/2015/gogo.slide#22