Live data from Hacker News

Go version 1 is released

blog.golang.org

71–80 of 168 posts

Re: Go version 1 is released

#73

Earlier quoted context omitted.

Go 4.1.1 will now be rebranded 'Golaris 1.0'

Golaris has a nice ring to it actually... Rolls of the tongue a bit - however sounds more like an ailment. "Oh, I got the golaris! better get an ointment for this"

You mean an app ointment ?

Re: Go version 1 is released

#74

Earlier quoted context omitted.

> I'm still wishing that we could embed Go into a multithreaded c application, just like we can with the JVM and Mono. I would like to use Go as a "scripting" language. What?

I believe the post is referring to something like http://docs.oracle.com/javase/7/docs/technotes/guides/jni/sp...

I was not aware that was possible... A little terrifying, actually.

Re: Go version 1 is released

#76
post #60

Well, they got (at least) one thing exactly right: Doing away with the "toolchain". Having one command that can figure out how to build your code, including downloading external dependencies, is really nice. Pity about the whole "not having generics" thing though.

With interfaces, it's pretty simple to replicate patterns like a Container or Channel, to borrow common Java syntax. Personally, I like how it forces you to think about parametricity whenever you want polymorphism, like most functional languages.

Re: Go version 1 is released

#78

"We're announcing Go version 1, or Go 1 for short" I foresee the next version being considered harmful.

Or they can label versions like sun, so that nobody will know for sure if they're using Go 2 or Go 1.2 or Go Enterprise Edition or Go Standard...

Or they could label versions like LaTeX, using a mathematical constant's decimal places.

For root 2: Version 1, Version 1.4, Version 1.41, etc.

Re: Go version 1 is released

#79
post #60

Well, they got (at least) one thing exactly right: Doing away with the "toolchain". Having one command that can figure out how to build your code, including downloading external dependencies, is really nice. Pity about the whole "not having generics" thing though.

With interfaces, it's pretty simple to replicate patterns like a Container or Channel , to borrow common Java syntax. Personally, I like how it forces you to think about parametricity whenever you want polymorphism, like most functional languages.

But, unless I'm missing something, it's missing the supporting bits you get in a nice functional language, like algebraic datatypes and pattern matching, which make that style much more pleasant.

Of course, most of the functional language DO have generics, and full type inference to boot, also.

Post reply on HN