Is this the current one? https://docs.google.com/document/d/16Y4IsnNRCN43Mx0NZc5YXZLo...
Go 1.4 is released
71–80 of 265 posts
Re: Go 1.4 is released
#72Nice. Now all I need is for someone to turn https://github.com/jcla1/gisp into a slightly more complete LISP and I'll have a nice environment for all kinds of ARM systems. Edit: typo/autocorrect
Re: Go 1.4 is released
#73Re: Go 1.4 is released
#74Can someone give me a compelling reason to start programming in Go? My default language at the moment is C, or C++.
Re: Go 1.4 is released
#75> The most notable new feature in this release is official support for Android. Using the support in the core and the libraries in the golang.org/x/mobile repository, it is now possible to write simple Android apps using only Go code. This is fantastic! Are there any example Android apps released by the Go team to help get started ?
If go code can now run on android, the go compiler can run on it...? Allowing go coding on-the-unit.
Re: Go 1.4 is released
#76> The most notable new feature in this release is official support for Android. Using the support in the core and the libraries in the golang.org/x/mobile repository, it is now possible to write simple Android apps using only Go code. This is fantastic! Are there any example Android apps released by the Go team to help get started ?
https://github.com/golang/mobile/tree/master/example
Re: Go 1.4 is released
#77Re: Go 1.4 is released
#78Can someone give me a compelling reason to start programming in Go? My default language at the moment is C, or C++.
Re: Go 1.4 is released
#79Can someone give me a compelling reason to start programming in Go? My default language at the moment is C, or C++.
A really crisp way to model concurrency. Most real world performance problems stem from the inability to model concurrency correctly. I also found it's faster to read the library code than the docs. A lot of thought has gone into making the language and library clean and easy to understand.
Re: Go 1.4 is released
#80There is a new range syntax[1]. The release notes say it's rarely used, but makes code cleaner. In which cases would the syntax be useful? [1] https://golang.org/doc/go1.4#forrange