Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Go 1.4 is released

blog.golang.org

Post reply on HN
Print view View original

121–130 of 265 posts

Re: Go 1.4 is released

#121

Post by Morgawr »

bsaul wrote: post #85
alfiedotwtf wrote: post #6

Earlier quoted context omitted.

And now things just got interesting. I'll put my money on the availability of Go on Android being the catalyst for its future hockey stick growth.

I would be extremely surprised to see a language having no class, no inheritance and no good IDE become successfull in modern app development. Android devs are used to such a different type of programming, i don't expect them to accept banging their heads on so many walls for such little gains. Ps : my stand is the opposite for server side dev.

Maybe this will help people (like me, for instance) who are disgusted by the overengineered OOP-heavy approach of most Java frameworks but enjoy the concise and elegant simplicity of languages like Go to finally move over and try out Android development.

Re: Go 1.4 is released

#122

Post by pjc50 »

teddyh wrote: post #65
paddyoloughlin wrote: post #59

Earlier quoted context omitted.

How would communities around anything come to exist if everyone had the same attitude?

Look at how the communities around languages like Basic, Pascal, C, Lisp and Python have developed. They were, from the beginning, open with development, releasing early and often, and were explicit about readily accepting large contributions from outsiders (and really did so). The creators were always open to the possibility that they themselves might not be the eternal keepers of the language, which allowed competi…

I don't think this is true of C. The original compilers were AT&T proprietary, surely? Hence the need for multiple competing implementations.

Re: Go 1.4 is released

#123

Post by Morgawr »

howeman wrote: post #66
codexon wrote: post #58

Earlier quoted context omitted.

You can still get segfaults in Go. "panic: runtime error: invalid memory address or nil pointer dereference"

But you also get a stack trace without needing an IDE and debugger.

I've been working with Go daily for a few months now at my job and I'd like to point out that Go stack traces have a really big signal to noise ratio. There is a lot of cruft that mostly nobody cares about and sometimes it can be hard to pinpoint exactly where something crashed (at which line) with a panic.

Just saying, they should probably improve it to be less verbose and more concise.

Re: Go 1.4 is released

#124

Post by neoeldex »

drvd wrote: post #91
Cyph0n wrote: post #79

Earlier quoted context omitted.

Doesn't that mean that the docs are lacking?

No. Docs are very complete, readable and helpful.

I disagree, i find it hard to find useful information, and proper examples of usage are very rare.

Usually it's a list of methods on a package.

Re: Go 1.4 is released

#125

Post by Morgawr »

teddyh wrote: post #120
dsymonds wrote: post #62

Earlier quoted context omitted.

Have you actually observed the Go community and how Go has been developed over the last five years? What you are saying are fair concerns in the abstract, but I cannot reconcile them with the reality of how the Go project operates. You also seem unusually hung up on its name. It's not like it's called Google Programming Language All Access.

I see from another comment that this release first happened, and then , afterward , the release was pushed to its “official” Git repository. This is not the way real open projects do releases, and instead indicates that the real development is done in-house and the code thrown over the wall. A name is important, as it is a symbol . As long as the language is called “Go”, Google will always have power over it, no matt…

>This is not the way real open projects do releases, and instead indicates that the real development is done in-house and the code thrown over the wall

There are several projects that are free and open source, wildly available to every platform, hacked upon by hundreds of people, that still do cycle releases and development behind the back of most developers and only release full .tar.gz archives with sources after a milestone is reached.

I might be wrong but iirc bash is one of those projects (or at least was), I seem to recall people complaining about it during the shellshock issue. The GNU libc might be another but I'm not sure.

Re: Go 1.4 is released

#126

Post by teddyh »

leaveyou wrote: post #93
teddyh wrote: post #65

Earlier quoted context omitted.

Look at how the communities around languages like Basic, Pascal, C, Lisp and Python have developed. They were, from the beginning, open with development, releasing early and often, and were explicit about readily accepting large contributions from outsiders (and really did so). The creators were always open to the possibility that they themselves might not be the eternal keepers of the language, which allowed competi…

I think you should do what you ask to be done. You fork Go under a new name, create a community with the same objectives as yours around it, be competitive and develop the language further and then reap the satisfaction. If there is a significant need for your ideas I'm sure the developers will join you (otherwise you will have the best proof that your idea is just not good enough for many others). Personally I'm ver…

You misunderstand me, please re-read what I wrote. Nowhere did I call for the forking of Go. On the contrary, I specifically wrote that it was unrealistic to even envision it, since it would not work as long as Google sponsored more into its development that I could do with the fork, and as long as Google was perceived as a more stable future sponsor of said development.

What I wrote was that I, personally, would not use Go as long as its development was perceived to be controlled and paid by Google. Forking Go would not ameliorate this in any way, unless it was successful, which would be extremely unlikely.

Re: Go 1.4 is released

#127

Post by pjc50 »

_RPM wrote: post #5

Can someone give me a compelling reason to start programming in Go? My default language at the moment is C, or C++.

You can write a network-facing application and the language will help rather than hinder you in making it secure.

Re: Go 1.4 is released

#128

Post by teddyh »

diakritikal wrote: post #96
teddyh wrote: post #65

Earlier quoted context omitted.

Look at how the communities around languages like Basic, Pascal, C, Lisp and Python have developed. They were, from the beginning, open with development, releasing early and often, and were explicit about readily accepting large contributions from outsiders (and really did so). The creators were always open to the possibility that they themselves might not be the eternal keepers of the language, which allowed competi…

Your assertions are at odds with everything observable with regards to development of the Go language.

I freely admit that I do not know the intimate details of Go development, but my point is that they are almost irrelevant. Go is still perceived to be controlled by (and therefore is controlled by) Google. How much that is actually true is almost irrelevant until the perception changes. And with a name like “Go”, Google likely has no intention or wish for that perception to change.

I mean, can anyone claim that an internal developer at, say, Microsoft or Apple could develop programs in Go and have them become used for large parts of the internal company infrastructure without it becoming politically sensitive, just as if they had chosen, say, C? Until that happens, Go is not an obviously-neutral platform, and I therefore have no desire to use it.

Re: Go 1.4 is released

#129

Post by lmm »

_RPM wrote: post #5

Can someone give me a compelling reason to start programming in Go? My default language at the moment is C, or C++.

If garbage collection is acceptable, you'd learn more from trying OCaml - or even Haskell, if you want to really expand your comfort zone. I'm not saying don't learn Go eventually, but for the "second language" you should try something more different from C/C++ so you get more of an idea of the range of stuff out there.

Re: Go 1.4 is released

#130

Post by bsaul »

Morgawr wrote: post #121
bsaul wrote: post #85

Earlier quoted context omitted.

I would be extremely surprised to see a language having no class, no inheritance and no good IDE become successfull in modern app development. Android devs are used to such a different type of programming, i don't expect them to accept banging their heads on so many walls for such little gains. Ps : my stand is the opposite for server side dev.

Maybe this will help people (like me, for instance) who are disgusted by the overengineered OOP-heavy approach of most Java frameworks but enjoy the concise and elegant simplicity of languages like Go to finally move over and try out Android development.

Sure, the java bloated ecoystem is a real issue. Yet, imagine yourself building UI component without classes or inheritance ? Can't even say something like "my custom button is a special kind of android button, with just those two methods being overriden".

GUI is to me the field where inheritance actually makes a lot of things easier and natural. Now you may end up with something similar using struct inheritance and manually overriding function for the given type, but i doubt most devs will go past the first unsuccesfull attempts.

Post reply on HN