I want off Mr. Golang’s Wild Ride (2020) • Hacker News Board

Re: I want off Mr. Golang’s Wild Ride (2020)

#21

Post by styluss » Thu, Apr 28, 2022, 2:26 PM UTC

DrBazza wrote: post #8

andrew_ wrote: post #5

Earlier quoted context omitted.

Not a "Go guy" but I try to keep up on the news. They've since added generics and cleaned up some of this since 2020 yeah?

This submission came up because the article author is on twitter today complaining about golang and posted the submission link.

Link?

Re: I want off Mr. Golang’s Wild Ride (2020)

#22

Post by HL33tibCe7 » Thu, Apr 28, 2022, 2:27 PM UTC

Could this post be unflagged please? I don't think it satisfies any requirement for flagging.

Re: I want off Mr. Golang’s Wild Ride (2020)

#23

Post by fasterthanlime » Thu, Apr 28, 2022, 2:28 PM UTC

styluss wrote: post #21

DrBazza wrote: post #8

Earlier quoted context omitted.

This submission came up because the article author is on twitter today complaining about golang and posted the submission link.

Link?

Here it is: https://twitter.com/fasterthanlime/status/151945555551713690... (source: am fasterthanlime).

No idea what HN's policy is on posting links to Twitter, but since you asked. Also if the consensus here is that that 2020 rant is "unfair and toxic", that twitter thread is not going to go over well either!

Re: I want off Mr. Golang’s Wild Ride (2020)

#24

Post by badRNG » Thu, Apr 28, 2022, 2:29 PM UTC

Why was this post flagged?

Re: I want off Mr. Golang’s Wild Ride (2020)

#25

Post by CraigJPerry » Thu, Apr 28, 2022, 2:30 PM UTC

This should not be flagged, this is a well written article

Re: I want off Mr. Golang’s Wild Ride (2020)

#26

Post by gambler » Thu, Apr 28, 2022, 2:30 PM UTC

Go has a lot of issues. Some of them would be easily fixable if people promoting and developing Go actually admitted the problems. However, the fanbase usually acts as a cult pretending that issues are features. Thing is, just like broken, hackish dependency "management" had to be fixed (introducing tons of complexity for the sake of not destroying backward compatibility), other problems will have to be fixed as well. It will add even more complexity to the language.

For example, Go error handling is shit. People will attempt to fix it with generics now and that will create a lot of inconsistency between different APIs. Because of those inconsistencies the entire language will loose any possibility of elegant, high-level, pre-packaged solutions for certain things (like automated logging, recovery, etc.) This loss will be permanent and the vast majority of users won't even understand why some things are so hard.

Re: I want off Mr. Golang’s Wild Ride (2020)

#27

Post by 0xdeadb00f » Thu, Apr 28, 2022, 2:33 PM UTC

To say go's simplicity is a lie, then to go and and say this;

> This function signatures tells us a lot already. It returns a Result, which means, not only do we know this can fail, we have to handle it. Either by panicking on error, with .unwrap() or .expect(), or by matching it against Result::Ok / Result::Err, or by bubbling it up with the ? operator.

What the hell? I'm not a rust dev. I have no idea what half of this means. "bubbling up"? What the fuck even is that?

Re: I want off Mr. Golang’s Wild Ride (2020)

#28

Post by chimen » Thu, Apr 28, 2022, 2:34 PM UTC

Before clicking the link I knew "Mr. Rust's Wild Ride" will be waiting for me on that article. Welcome to the hype train, 3rd edition: Ruby -> Node -> Rust. Everything else is just, well, inferior and I'm going to bash its brains out. Needs some "Rust" in the title.

Re: I want off Mr. Golang’s Wild Ride (2020)

#29

Post by Rygian » Thu, Apr 28, 2022, 2:35 PM UTC

0xdeadb00f wrote: post #27

To say go's simplicity is a lie, then to go and and say this; > This function signatures tells us a lot already. It returns a Result, which means, not only do we know this can fail, we have to handle it. Either by panicking on error, with .unwrap() or .expect(), or by matching it against Result::Ok / Result::Err, or by bubbling it up with the ? operator. What the hell? I'm not a rust dev. I have no idea what half of…

"Bubbling up" is the default in C++, when the code you call throws an exception and you don't have a try/catch for it.

Re: I want off Mr. Golang’s Wild Ride (2020)

#30

Post by [deleted] » Thu, Apr 28, 2022, 2:36 PM UTC

0xdeadb00f wrote: post #27

To say go's simplicity is a lie, then to go and and say this; > This function signatures tells us a lot already. It returns a Result, which means, not only do we know this can fail, we have to handle it. Either by panicking on error, with .unwrap() or .expect(), or by matching it against Result::Ok / Result::Err, or by bubbling it up with the ? operator. What the hell? I'm not a rust dev. I have no idea what half of…

[deleted]