Google Go Capturing Developer Interest

angry tapir writes with news that Google Go seems to be cutting a wide swath through the programming community in just a short time since its early, experimental release. While Google insists that Go is still a work in progress (like so many of their offerings), many developers are so intrigued by the feature set that they are already implementing many noncritical applications with it. What experiences, good or bad, have you had with Google Go, and how likely is it to really take over?

Comments

who's using it?

[larry bagina]

"C++ is too hard, I'll use java. java is too hard, I'll use C#. C# is too hard, I'll use python. Python is too hard (boner?), I'll use ruby. ruby is too hard, I'll use Go." -- GoFanBoy (formerly RubyFanBoy, formerly PythonFanBoy, formerly ...)

Re:Name

[schon]

Except that in order for a non-registered trademark to be valid, it must be well known.

Sorry, but "hey, I created a language - it was used by both me *and* my ex-girlfriend's dog five years ago" doesn't cut it.

Re:Go fuck yourself

[dskoll]

I'll let you know if/when my program halts...

Nirvana Quest

[strangeattraction]

I was one of those developers chafing at the bid to get my hands on Go. Once I started I never looked backed. I was able to write my own version of HelloWorld in half (that is 1/2) the time it took me to do it in C and it was bug Free with no memory leaks. I think that pretty says it all. If you're looking for a programming language that solves all your coding problems look no further. Now that I have abandoned Java my manually linking programs with xml skills have declined sharply. Similarly after abandoning Lisp my ability to match parenthesis's has almost vanished. No matter, with Go I perceive the universe in my belly button.

Re:"many developers are so intrigued"

[roman_mir]

you don't think Go will go well? :)

I read the spec, I noticed that Ken Thompson is one of the designers and this:

This approach makes for clean-looking, semicolon-free code. The one surprise is that it's important to put the opening brace of a construct such as an if statement on the same line as the if; if you don't, there are situations that may not compile or may give the wrong result. The language forces the brace style to some extent.

- if this is not done on purpose, I'll eat my hat (which by coincidence is currently made of some eatable stuff I think).

I know why there is this new language now, forget about everything else, Ken just wanted to make a point of the correct style of opening braces and he came up with a language that does not allow you to do any different!