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

From Node.js to Go

bowery.io

Post reply on HN
Print view View original

191–192 of 192 posts

Re: From Node.js to Go

#191

Post by 4ydx »

wwweston wrote: post #174
engendered wrote: post #162

Earlier quoted context omitted.

If being able to get things out the door anyway This is specious logic. People are not being told to use Go grudgingly because it is mandatory. It isn't a required component of some entrenched industry dictum. The only possible reason someone would choose Go is because, somehow, it is advantageous to their process. And we've seen an enormous number of success stories with Go recently -- all people choosing to use it…

> People are not being told to use Go grudgingly because it is mandatory. It isn't a required component of some entrenched industry dictum. You're registering this objection on the basis of JS's privileged status in the browser; I'm invoking it because of The Fine Article's comparison with JS on the server, where it's adopted as voluntarily as any other language -- and where, yes, despite claims that event-driven/cal…

You almost sound angry that other people are enjoying and having success with a language that you loath. I would wager that you simply are not taking enough time to shift your thought process to a state that is more in line with what is available in golang.

Re: From Node.js to Go

#192

Post by sagichmal »

azth wrote: post #179
sagichmal wrote: post #157

Earlier quoted context omitted.

> I get lost trying to figure what > the happy path behavior is. The happy path is idiomatically at indent level 0.

Except when it's if x, err := doSomething(); err != nil { }

...the happy path there is intend level 0?

    if err := doSomething(); err != nil {
        return fmt.Errorf("something failed: %v", err)
    }
Or,

    x, err := doSomething()
    if err != nil {
        return fmt.Errorf("something failed: %v", err)
    }
    
    log.Print(x)
Post reply on HN