Live data from Hacker News

Go 1.6 is Released

blog.golang.org

181–190 of 367 posts

Re: Go 1.6 is Released

#181

Earlier quoted context omitted.

You don't have to "get" anything. If Java works for you, great!! Go just works better for some of us, and that's all the justification we need.

This type of comment is common, but specious. It sounds nice: "what works for you; great! this works for me" but it undermines a large category of important discussions: e.g. analyzing which, out of several competing discussions, is a better fit for large classes of people, or on average. In other words, I think this sort of comment strays too far in the direction of niceness, and tends to undermine simple, and desir…

> TL;DR being nice and polite is over-rated. Some things are wrong and it is helpful to say so.

And thus continues the never ending cycle of "You're wrong! No you're wrong!"

Re: Go 1.6 is Released

#182

Earlier quoted context omitted.

> The mental image of a huge ram sucking IDE with code completion for frameworks is simply incompatible with > what I would consider the ideal creative process for me as programmer. Java has long been my primary professional language, and over the past few years Go has taken on a strong secondary niche at my job. I'm big fan of both, and tend to play Switzerland in arguments between them. That being said, the best Go…

Can you explain why using a plain text editor for a typesafe language is a bit daft?

That may be stated too strongly, but the argument is in a statically typed language you go to all the trouble to provide the compiler with sufficient amounts of information, but then don't leverage that in your editor.

E.g. if you call a statically resolved function, your IDE should be able to take you to the function's definition.

Re: Go 1.6 is Released

#183
post #52
post #25

Earlier quoted context omitted.

Not to start a flamewar or anything, but what about clojure (or any lisp for that matter, I just like the CLJ ecosystem) doesn't vibe with your 'minimal syntactic sugar' and other requirements?

Oh, don't mistake my comment for favorable opinion. I only wrote a few hundred lines of Go in my life. It worked well for the particular problem I was solving, but I'm really more of a C/C++ guy. The problem with lisps is that you need to know lisp, and relatively few people do. It also requires a different approach to program design. It may or may not be a better approach, but the fact is, that's not what most peopl…

The little secret of Lisp is that you can use it pretty much as an imperative language, even though it also enables functional programming. The main barrier is that Lisp is taught as a functional programming language, and many believe that this is the only way you should use it.

Re: Go 1.6 is Released

#184

Earlier quoted context omitted.

I'm not being negative. I was confused by the unfamiliar anthropomorphic terminology being applied to an artifact. I take away a sense that "opinionated" seems to be an idiom popular within the golang community for a sense of principled design along the lines of Smalltalk's message passing, Lisp's homoiconicity, Haskell's purity from side effects, and so on.

> I'm not being negative. I was. My previous message is an arbitrary combination of HN clichés, of which "opinionated" is one. It's gibberish, devoid of content but written in a fashionable way. It got zero down-votes so far. Maybe something to think about.

I felt like I owed the world a response to your question even though the first sentence made no sense to me whatsoever. I guess that "opinionated" makes no less sense as a characterization of an artifact than "ambitious" or "stupid" does, so I'm going to have to learn to live with it, but it's one of those things like "performant" or "impactful" that will make me cringe if I ever catch myself saying it. Anyway, thanks for the response, my comrade-in-downvotes.

Re: Go 1.6 is Released

#185
post #139
post #137

Earlier quoted context omitted.

No floats?

No functional programming, or language features borrowed from there.

Which is kind of a shame, since many of those concepts would complement the strengths of Go quite nicely -- i.e., a pure goroutine that had no visible side effects apart from channel activity would help enable automatic remote execution in a cluster.

Re: Go 1.6 is Released

#186
post #6

Earlier quoted context omitted.

The more I dig into type coercion and interfaces the less I miss generics. Still not 100% there, but for day to day the things I used to use generics for have been replaced by alternates. I still wish I never had to write `interface{}` though. Debugging absolutely needs work though.

Is "alternates" a euphemism for "code duplication?"

Or code generation?

Re: Go 1.6 is Released

#187

Earlier quoted context omitted.

Actually you can: https://play.golang.org/p/a-qhe_vRvo

Oh my god...is that new? I swear I've tried that and it didn't work. You are my new hero. [edit] Though maybe I was thinking of adding parameters like https://play.golang.org/p/FKUMlQzCI5 In any case 'thebaer continues to be my hero.

It's how html/template.Must works, isn't it?

We have a small library of functions for sweeping up error returns, and for collecting errors from multiple functions and checking them all at once. It helps a lot.

Golang is very much on to something with it's "errors are values" philosophy, but I'd be the first to acknowledge that it's not a fully baked philosophy. It is weird to discover fundamental things about how to structure basic code several years into writing in a language, but that happens somewhat regularly with Go.

Re: Go 1.6 is Released

#188

Earlier quoted context omitted.

Actually you can: https://play.golang.org/p/a-qhe_vRvo

Thanks, I've never seen that used and didn't know they special-cased it until I found https://golang.org/ref/spec#Calls . I wonder why it's not more common...

I'm sure there are good uses for it, but I personally haven't found one yet. I mostly use Go's multiple return values to also return errors -- and that's really like using checked exceptions in Java. So whether it's a try/catch or an if statement, you have to code for these things one way or another.

Re: Go 1.6 is Released

#189

Can anybody tell me if you can run Go in Chrome using the NaCL stuff? I remember there was talking of it a few years ago but I don't know if anything ever came of it. A google seach show that you could build for NaCal in Go 1.3 but only run it in special builds not Chrome itself.

As you can see on https://github.com/golang/go/wiki/NativeClient , there is no PNaCl support, which means it is only available in the Chrome Web Store.

Re: Go 1.6 is Released

#190

Earlier quoted context omitted.

I don't like Oracle. I don't like the JVM. I refuse to learn Java because I personally have a strong bias for native, compiled code. In fact, I really dislike everything about the Java way of programming. The mental image of a huge ram sucking IDE with code completion for frameworks is simply incompatible with what I would consider the ideal creative process for me as programmer. That being said, if I were starting a…

For my money, Java is a pretty good language; there are only a couple of things that I think were real mistakes in the core language. And the JVM certainly performs. But the ecosystem around Java is very complex and hard to manage. Dealing with JVM configuration, webserver configuration, build system configuration, IDE configuration and God knows what else takes up all kinds of brain-space. And every so often the com…

I'm lucky that I develop Java CLI apps that only I need to maintain and one other person. But damn there are days in which I scratch my head and wonder why I have to write so much code to do simple things. But on the other hand my best work has been writing Java apps.

I have a love hate relationship with Java. I do have Java apps that runs 24x7, day after day without failure.

I think I protest too much.

Post reply on HN