111–120 of 168 posts
Earlier quoted context omitted.
Nonsense. You would hate Android written in Go, because of the GC pauses. Dalvik has a concurrent garbage collector; Go has a stop-the-world one.
Only because that's all that's been implemented. They're well aware of GC and compiler optimizations being a target for future versions of Go.
Earlier quoted context omitted.
My god. Go is _so_ much fun to program. Apart from it's technical pedigree this is its most remarkable feature.
Essential question: what makes it fun?
For me it's the language's simplicity. There are no hidden surprises in the spec. It's short, clean and easy to memorize. The syntax is clear and (for the most part) un-intrusive. Some of it's idioms really force you to think about what you have learned in other languages. And then either forget any of that ever happened, or at the very least become a critical thinker about the usefulness of these things. For example: the standard inheritance based OOP model.
Go simply allows me to 'get shit done' fast and without having to jump through hoops. It's very much like a breath of fresh air in what was quickly becoming a stale and obnoxious development environment (for me at least).
Edit: I would add that I do not particularly like evangelising about anything; that includes Go. It is beautiful for what it is. but by no means should it be considered a silver bullet. If your current tool chain(s) and language(s) work for you, by all means continue to use them. Go has its strengths and its weaknesses that should always be considered at the same time.
The right tool for the right job and all that.
Earlier quoted context omitted.
My god. Go is _so_ much fun to program. Apart from it's technical pedigree this is its most remarkable feature.
Essential question: what makes it fun?
I don't like to spend time on irrelevant things like "why the binary does not link", "in which shared library this undefined symbol is located" or "how to parse XML", or even plain "why it does not work".
With Go I _usually_ have a predictable process of writing a program, when simple things are simple and complex things are reachable. It makes me happy.
Earlier quoted context omitted.
The "install go" link on the "Go offline" page gives "file not found: /go/install".
You do realize that telling HN is not an appropriate way to have that bug fixed, right? I know lots of Googlers hang out here, but your comment is buried pretty deep.
What happened to the ebnf package?
What happened to the ebnf package?
What happened to the ebnf package?
Anyone care to share their experience writing something in go? I've toyed with it but not built anything in production. FWIW, the go dashboard ( https://godashboard.appspot.com/ ) has a number of interesting projects.
SVGo paper from SVG Open 2011: (https://www.svgopen.org/2011/papers/34-SVGo_a_Go_Library_for...)
Samples: (http://www.flickr.com/photos/ajstarks/sets/72157623441699483...)
Earlier quoted context omitted.
My god. Go is _so_ much fun to program. Apart from it's technical pedigree this is its most remarkable feature.
Essential question: what makes it fun?
Earlier quoted context omitted.
I have written a bit of Go. It strikes me as sort of the Unix of programming languages. It's very opinionated, takes some overarching concepts, mostly channels and interfaces, then proceeds to thoroughly not care what you think about it: refuses to have generics, lambdas and tail-call recursion like a pro. The polar opposite of design by committee. It even enforces a True Brace Style to keep the parser simple! Techni…
Why would you move from Haskell to Go? There's a night-and-day difference between them. I don't understand why you'd switch to a language because of the features it's lacking, unless you think those features are a bad thing (and I have yet to see a reason why generics and TCO are a bad thing).