Lies we tell ourselves to keep using Golang

Post by etblg » Fri, Apr 29, 2022, 3:59 PM UTC

Thaxll wrote: post #154

I'm just wondering why the author keeps making those articles about strongly disliking Go, ok we get it your favorite language is Rust, you don't like Go. Why does the author does not move on, exactly? "Fine. It may well be that Go is not adequate for production services unless your shop is literally made up of Go experts (Tailscale) or you have infinite money to spend on engineering costs (Google)." This is really w…

Post by jayd16 » Fri, Apr 29, 2022, 3:59 PM UTC

paskozdilar wrote: post #32

kitd wrote: post #12

The author obviously doesn't like Go. Ok, he can have his own opinions. I've been coding professionally since 1987, using everything from mainframe assembler, Fortran, C, VB, Java, C++, to most recently Go. IMHO, the language itself plays a smaller role in its usefulness than most think. As important is the tooling, stdlib, ecosystem, community and "StackOverflow"-ability. Go has a few warts, like every language, but…

For me, the goroutines + channels + select is what makes Go leagues above any other popular language. As far as I know, no other popular language allows you to read from multiple queues at the same time, which is an extremely useful pattern in concurrent programming. The only way to "select" from multiple sources in other languages is to use some kind of poll/select syscall on file descriptors - and even that is very…

Post by kevinmgranger » Fri, Apr 29, 2022, 4:00 PM UTC

wara23arish wrote: post #89

roblabla wrote: post #79

Earlier quoted context omitted.

> I thought everything was handed out as copies in go by default unless a pointer was being passed. So this would make it “easy” to tell whether you are mutating a object or not. The first bit is correct. The point the article makes is that, to know whether a variable is potentially mutated, you have to go look at the signature of any function called on it. E.G. you can't just look at main and "know" whether a will g…

i feel like that C example isnt fair cause you cant have functions bound to types right?? youre not calling change(a) but instead calling a.change(). i havent learned any rust yet, im waiting till im a little better at go so i can be comfortable at work before doing so:) whats the advantage of creating a function of type struct a rather than creating the C equivalent of change(obj structAtype) ? to me now, it seems t…

    type Foo struct {
        bar int
    }

    func (f Foo) mutate() {
        f.bar = 2
    }

    func main() {
        f := Foo{bar: 1}
        f.mutate()
        fmt.Println(f.bar) // 1
    }

Post by gjsman-1000 » Fri, Apr 29, 2022, 4:01 PM UTC

brundolf wrote: post #214

gjsman-1000 wrote: post #169

Earlier quoted context omitted.

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?

To play devil's advocate: this author is known for often having a combative style. There's usually lots of good substance alongside that style, but the tone is what it is, and you could argue that it's needlessly incendiary. (Though in their defense, the post yesterday was self-described at the very top as "a proper rant") HN is a powder keg of emotions about programming languages, and fasterthanlime's posts tend to…

Post by andrelaszlo » Fri, Apr 29, 2022, 4:01 PM UTC

Thaxll wrote: post #154

I'm just wondering why the author keeps making those articles about strongly disliking Go, ok we get it your favorite language is Rust, you don't like Go. Why does the author does not move on, exactly? "Fine. It may well be that Go is not adequate for production services unless your shop is literally made up of Go experts (Tailscale) or you have infinite money to spend on engineering costs (Google)." This is really w…