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

Why I Don't Like Golang (2016)

teamten.com

Post reply on HN
Print view View original

291–297 of 297 posts

Re: Why I Don't Like Golang (2016)

#291

Post by pdimitar »

apta wrote: post #142
jayd16 wrote: post #64

Earlier quoted context omitted.

I see this complaint against Java a lot. If you're going to slum it in a language with no ecosystem so you don't feel overwhelmed, why not just use less of the Java ecosystem?

These complaints are usually by people who have not been using modern Java, or who have just been reading or hearing unsubstantiated claims about it. Or who haven't worked in large golang projects to see all the mess it brings with it because of how underpowered it is. Look up libraries like Spark[1] or Javalin[2] and you get something quite light weight. Or DropWizard[3] if you need something more holistic. That bei…

There hasn't been a single job advert in the last decade when I was being contacted for Java gigs that didn't involve dealing with legacy code and dependency injection spaghetti.

Everybody has legacy code. Modern Java doesn't mean much if your team is 2 years away from being able to use the modern stuff.

Re: Why I Don't Like Golang (2016)

#293

Post by matt_kantor »

weberc2 wrote: post #279
matt_kantor wrote: post #275

Earlier quoted context omitted.

The pebble is still there, but most people learn to walk in such a way that they don't put their full weight on that part of their foot. This might not be the most efficient way to walk, but once you've done it for a while it starts to feel natural.

And then you switch to Go thereby removing the metaphorical pebble, but you have to relearn how to walk efficiently. See how pointless this is?

I guess you just don't like the metaphor?

I thought you had misinterpreted it, so I was trying to help clarify by extending the metaphor. In case we're still misunderstanding each other: the pebble is the language's warts, which you can't remove, only avoid or work around. Every language has its warts, but we're talking about Go's here.

You don't have to be rude about it.

Re: Why I Don't Like Golang (2016)

#294

Post by Boxxed »

apta wrote: post #148
Boxxed wrote: post #99

Earlier quoted context omitted.

100% agreed -- it's crazy to me how much stuff you can just sweep under the rug when you have fast compilation, a decent debugger, static binaries, and so on. I always tell people, "I love everything about Go except for the language."

> have fast compilation, a decent debugger, static binaries, and so on. See Java[1], C#[2]. Both have good compilation speeds (which don't really matter when you have incremental compilation anyway), as well strictly superior debuggers. [1] https://quarkus.io/ [2] https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen...

Oh thanks, haven't heard of those languages.

Re: Why I Don't Like Golang (2016)

#295

Post by weberc2 »

matt_kantor wrote: post #293
weberc2 wrote: post #279

Earlier quoted context omitted.

And then you switch to Go thereby removing the metaphorical pebble, but you have to relearn how to walk efficiently. See how pointless this is?

I guess you just don't like the metaphor? I thought you had misinterpreted it, so I was trying to help clarify by extending the metaphor. In case we're still misunderstanding each other: the pebble is the language's warts, which you can't remove, only avoid or work around. Every language has its warts, but we're talking about Go's here. You don't have to be rude about it.

I wasn't being rude, and I understood your point. I was pointing out that the metaphor can as easily be used to support Go's position as the critics' position. The metaphor lacks substance. Criticism != rude.

Re: Why I Don't Like Golang (2016)

#296

Post by bluquark »

886 wrote: post #199
bluquark wrote: post #40

Earlier quoted context omitted.

Kotlin and Swift are both currently encroaching on Go's server-side use cases. For example, Go's star feature, goroutines, has recently been cloned by Kotlin. They are at least as equally pleasant to program in, and they're hitched to major client platforms which means they improve faster and will definitely have a pool of trained developers in the long term.

Points taken. I am full time on Go since few years ago and before that I was 100% Java. Haven't really kept myself up-to-date with the Java land. But from my experience with Java, Go, and Python, I find Go a very versatile programming language. Being able to compile binaries means it's great for infrastructure deployments and CLI tools. Goroutines, concurrency, and etc make it a great choice for server/micro service…

JVM is gaining self-contained deployable package support, and as of recently, Kotlin supports a mode with LLVM-based native code generation.

IMO, the fundamental advantages of Go over competing languages in the long run are its fast compile time and its combination of native code+garbage collection.

Re: Why I Don't Like Golang (2016)

#297

Post by matt_kantor »

weberc2 wrote: post #295
matt_kantor wrote: post #293

Earlier quoted context omitted.

I guess you just don't like the metaphor? I thought you had misinterpreted it, so I was trying to help clarify by extending the metaphor. In case we're still misunderstanding each other: the pebble is the language's warts, which you can't remove, only avoid or work around. Every language has its warts, but we're talking about Go's here. You don't have to be rude about it.

I wasn't being rude, and I understood your point. I was pointing out that the metaphor can as easily be used to support Go's position as the critics' position. The metaphor lacks substance. Criticism != rude.

"See how pointless this is?" sounded very snippy in my head, but perhaps I didn't read it charitably enough.
Post reply on HN