This shouldn't be flagged...
No post body was provided.
Lies we tell ourselves to keep using Golang
161–170 of 561 posts
Re: Lies we tell ourselves to keep using Golang
#162No post body was provided.
Re: Lies we tell ourselves to keep using Golang
#163Earlier quoted context omitted.
Can you clarify further? Otherwise this seems like a shallow dismissal, which is against our HN community guidelines, and makes for uninteresting discussion.
Programming languages have a large amount of irreducible complexity. A page long spec for a language more complex than Brainfuck cannot represent the critical distinctions correctly. Without that clarity, you end up with incompatible, spec-compliant implementations. This is a disaster, and so below a certain point relative to language complexity a shorter spec is simply wrong.
> Without that clarity, you end up with incompatible, spec-compliant implementations.
The Go team officially maintains two implementations, gc and gccgo, to ensure that implementation doesn't end up ruling over the specification as has happened in other languages. There are also other third party implementations, including tinygo.
Which spec-induced incompatibilities across these implementations are you referring to?
Re: Lies we tell ourselves to keep using Golang
#164You guys flagged this? That is not the move of a vibrant, growing, confident community. I’m no fan of the Rust jihad myself, but this isn’t spam or hate speech or whatever. That is a super weak move.
I guess it's because it's not anything that hasn't been said before. Go is easy to start with and gets harder as you debug deep problems. Rust is very hard to start, then it gets easier over time. This has been said in many other threads, and we all know it's true.
Re: Lies we tell ourselves to keep using Golang
#165The flagged feature needs to be tweaked on HN; it's being used far too often to censure opinions others simply do not agree with.
It's pretty much the whole culture now, not just HN. Anything I don't agree with is an evil and must be stopped at any cost.
Re: Lies we tell ourselves to keep using Golang
#166Flagging this post strikes me as shameful censorship of an unpopular opinion. You may say it's the snark/anger/frustration that got flagged, but I suspect it would not have been flagged if the topic were different. Presuming the author is making bad-faith arguments for internet blog points goes against the spirit of HN. I prefer to draw my own conclusions, thank you. I normally expect HN to take the higher ground wit…
I am also surprised that a reasoned discussion like this gets flagged while comments calling it a "shitpost" are not.
Re: Lies we tell ourselves to keep using Golang
#167You guys flagged this? That is not the move of a vibrant, growing, confident community. I’m no fan of the Rust jihad myself, but this isn’t spam or hate speech or whatever. That is a super weak move.
Right now our only mechanism to indicate that we don't think a post is appropriate is to flag it. We don't have the ability to downvote posts that we don't feel meet the quality bar for being featured on HN.
Why is it flagged then? It is clearly an appropriate posting.
Re: Lies we tell ourselves to keep using Golang
#168Earlier quoted context omitted.
> As far as I know, no other popular language allows you to read from multiple queues at the same time Off the top of my head, that's certainly possible in Rust, C++ and Java - probably many others I just don't know about. That particular bit of concurrency goodness comes from the 70s, so you can be sure other languages picked it up.
If you could spare some time, would you please demonstrate an example? Any language of those mentioned would be OK.
Here's a Rust example, with tokio: https://play.rust-lang.org/?version=stable&mode=debug&editio... - I don't have time to come up with Java/C++ examples, but I'm sure others will.
(If your point was about it being _built into the language_, then it definitely stands, see the other discussion in the parent comment thread)
Re: Lies we tell ourselves to keep using Golang
#169I'm honestly surprised at the response to this article. I'm not involved in the Rust or Go spaces enough to have any strong opinions. This article was, yes, a little aggressive in tone but presented very honest and accurate information about a language that the author clearly has experience in. It seems like a lot of the people complaining in the comments didn't actually read the article. The author even explains how…
This is the second day in a row where a post about Go in a negative light was flagged. The first one was an extremely detailed criticism, maintained the front page, and was flagged like crazy. What gives?
Re: Lies we tell ourselves to keep using Golang
#170Earlier quoted context omitted.
Right now our only mechanism to indicate that we don't think a post is appropriate is to flag it. We don't have the ability to downvote posts that we don't feel meet the quality bar for being featured on HN.
Why is it flagged then? It is clearly an appropriate posting.
No post body was provided.