Live data from Hacker News

Go 1.5 Beta

golang.org

51–60 of 82 posts

Re: Go 1.5 Beta

#51
post #48
post #47

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

That suggestion is not really practical as you need to make the same requirement from all your third party libraries. While gcc will spend more time optimizing than go, the main reason for the speed difference at the moment IS unnecessary work done by the preprocessor because of the primitive importing.

Re: Go 1.5 Beta

#52
post #32
post #22

Earlier 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?

You could argue lots of long running server software has been compiled more times through development than it has been started in prod.

Re: Go 1.5 Beta

#54
post #53

Can 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

Rob Pike talks about it here: https://youtu.be/cF1zJYkBW4A?t=29m6s

Re: Go 1.5 Beta

#55
Really 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.

Re: Go 1.5 Beta

#56
post #25

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

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.

Re: Go 1.5 Beta

#57

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

Yep, the link should be https://golang.org/dl/.

Work is ongoing to make golang.org be HTTPS only.

Re: Go 1.5 Beta

#58
> The "stop the world" phase of the collector will almost always be under 10 milliseconds and usually much less.

Well 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

#60
post #53

Can 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

Here's an example: https://github.com/rsc/x86/blob/master/x86.csv#L37
Post reply on HN