The future's looking bright for Go.

I've recently been looking at some new languages: Scala, Haskell, Clojure, Node.js etc. Go was the only site to put code samples (live ones at that) on their front page.

Language/framework creators take note: The first thing I want to see on your site is what the code looks like. How to install it is a distant second (I can look it up once you've convinced me it's worth installing)

very happy to hear about the "go" command on the timeline. While I haven't really had much trouble building Makefile this has seemed one of the least elegant parts of development with Go

Checkout the usage for ./go so-far here: http://code.google.com/p/go/source/browse/src/cmd/go/script....

Go 1 is a good idea. I just hope Go 2 is not considered harmful.

"The Go 1 release will be available in source and binary form for at least these platforms: ... Windows (2000 + later): amd64, 386"

I develop primarily on a Windows machine, so this is some good news.

I have only skimmed the page, but this caught my eye:

    Close is intended as a way for a sender to signal
    that no more values will be sent.  

    Go 1 will disallow close on receive-only channels.

It's currently quite a pain to get the most-recent Go release installed, and integrated into your development environment. I'd like to see Go v1 be more distribution-friendly. This is the biggest show-stopper for wider Go adoption.

I'd also like to see a built-in IDE analogous to Python's IDLE to lower the barrier-to-entry. IDLE is great for education.

I also think that Go needs to establish some sort of independent entity for the future development of the language. People need assurance that Go isn't going to go away if Google gets bored with it. Go hasn't crossed that rubicon yet, and this is another big barrier to adoption.

Submitted yesterday: http://news.ycombinator.com/item?id=3080027

undefined