Live data from Hacker News

What Golang Is and Is Not

danmux.com

121–130 of 279 posts

Re: What Golang Is and Is Not

#121
post #116
post #78

What we like to keep missing is that golang innovates not as a language, but as a tool to contribute to software project success. Project success in the software industry is abysmal, and we still keep thinking we can spin up another language that will contribute to project success because it let's us express ourselves in new ways. Well, how's that working out so far? The reason why golang appears to have such wide ad…

Go has been around nearly a decade with the backing of none less than Google and yet it remains a fairly fringe language. Elixir is on a much steeper adoption curve. So is Swift, but Elixir doesn't even have a tech heavyweight behind it.

Wikipedia says Elixir first appeared in 2012, while Go first appeared in November 2009. Go is not that much older than Elixir...so I don't buy your analysis. By time Go was four years old, it had much greater adoption than Elixir does today.

Re: What Golang Is and Is Not

#122
post #78

What we like to keep missing is that golang innovates not as a language, but as a tool to contribute to software project success. Project success in the software industry is abysmal, and we still keep thinking we can spin up another language that will contribute to project success because it let's us express ourselves in new ways. Well, how's that working out so far? The reason why golang appears to have such wide ad…

What we keep missing is that golang is not nearly as widely adopted as the blog traffic level would lead one to believe.

Re: What Golang Is and Is Not

#123

Earlier quoted context omitted.

As someone who writes Go every day for work, I can't agree that Go is simple. You may be confusing "simple" with "good". A simple solution to a complex problem may not be a good one. Go can be simple and still not a great solution because it pushes complexity to a higher level.

I think there's a difference between "simple" and "simplistic", and people don't often get it.

People rarely differentiate "complicated" and "complex". I get the feeling from GO that it was designed for making complex programs.

Re: What Golang Is and Is Not

#124
post #116
post #78

What we like to keep missing is that golang innovates not as a language, but as a tool to contribute to software project success. Project success in the software industry is abysmal, and we still keep thinking we can spin up another language that will contribute to project success because it let's us express ourselves in new ways. Well, how's that working out so far? The reason why golang appears to have such wide ad…

Go has been around nearly a decade with the backing of none less than Google and yet it remains a fairly fringe language. Elixir is on a much steeper adoption curve. So is Swift, but Elixir doesn't even have a tech heavyweight behind it.

Go 1.0 is released in March 2012 so it is not even half decade old.

Re: What Golang Is and Is Not

#125
post #57

Earlier quoted context omitted.

> haskell is among the best of them There is little need for this kind of absolutism. Citing a haskell as one the best language in a contest where op ask about rust and c++ is dangerous. To op : if your domain calls for modeling relatively 'type stable computation', and need strong correctness garanty, haskell is a great match.

How is it dangerous? Your qualifying remarks with regards to Haskell's domain make no sense. If you need a fast, compiled language with managed memory, high ease of development and a strong ecosystem then you can't go wrong with Haskell. 'Type stable computation' and a strong correctness guarantee are some added benefits of Haskell, though any strongly typed language (like for example Rust) will have these qualities.…

Haskell's runtime has one overriding attribute: laziness. If laziness is not desirable in your domain, Haskell is not a useful option

Re: What Golang Is and Is Not

#126
post #124
post #116

Earlier quoted context omitted.

Go has been around nearly a decade with the backing of none less than Google and yet it remains a fairly fringe language. Elixir is on a much steeper adoption curve. So is Swift, but Elixir doesn't even have a tech heavyweight behind it.

Go 1.0 is released in March 2012 so it is not even half decade old.

You know Go existed before 1.0, right?

Re: What Golang Is and Is Not

#127
post #48

Earlier quoted context omitted.

Go allocates on the heap unless it can prove something doesn't escape, in which case it's on the stack. Not explicit programmer control, but I think you can reasonably make it do what you want. Because it exposes pointers as a first-class concept, you also have good control of how data is laid out in memory (=> locality). It's not like Python or Java where everything is a pointer and gets spread out all over memory.

> Not explicit programmer control, but I think you can reasonably make it do what you want. Escape analysis, like any such analysis, gets much more difficult in the presence of higher-order control flow. Currently the Go compilers punt on higher order control flow analysis. And Go uses higher-order control flow in spades, due to its heavy reliance on interfaces. The end result is that lots of stuff is heap allocated.…

> That's not true for Java. Its generational garbage collector performs bump allocation in the nursery, yielding tightly packed objects with excellent cache behavior. Allocation in HotSpot is like 3-5 instructions (really!)

When I see this link I get different impression.

http://mechanical-sympathy.blogspot.com/2012/10/compact-off-...

It is only heavy use of sun.misc.Unsafe and unidiomatic coding style that give Java semblance of memory efficiency.

Re: What Golang Is and Is Not

#128
I'm not a Golang programmer, but the mere fact that GOOG decided Java for android is convincing enough that even GOOG does not believe in its Go.

(Frankly, I doubted that a little, until I realized Al-*-Go was not actually written in Go!)

Re: What Golang Is and Is Not

#129

I'm not a Golang programmer, but the mere fact that GOOG decided Java for android is convincing enough that even GOOG does not believe in its Go. (Frankly, I doubted that a little, until I realized Al-*-Go was not actually written in Go!)

Uhh, as someone who was there when Android began: There was no Go in 2005. And anyway, Go started with explicit about initial goal of being a server-side language, with choices (eg, only static linking) appropriate for that goal.

Re: What Golang Is and Is Not

#130
post #124

Earlier quoted context omitted.

Go 1.0 is released in March 2012 so it is not even half decade old.

You know Go existed before 1.0, right?

The question was about adoption curves, and i think version number is a signalling factor in adoption.

Pre-1.0 version number would certainly hamper adoption in my $DAYJOB.

Post reply on HN