Side-by-side Nim and Go

Re:Side-by-side Nim and Go by voidlogic on Friday April 10, 2015 @10:50AM (#9354693)

Not only that, on LOC is the goal; the Go code isn't written in most terse form, there are numerous unnecessary newlines and they do things like:

Examples:

    cmd.Stdout = os.Stdout
    cmd.Stderr = os.Stderr

    cmd.Stdout, cmd.Stderr = os.Stdout, os.Stderr

and:

    if open == 0 {
        fmt.Println("ok")
    } else {
        fmt.Println("not ok")
    }

vs.

    if open == 0 {
        fmt.Println("ok")
        return
    }
    fmt.Println("not ok")

[ Parent | on HN ]

Re:Side-by-side Nim and Go by jbooth on Friday April 10, 2015 @11:23AM (#9354926)

Your first example is a great counter-point to the talk above about "if more stuff can fit on the screen it's easier to understand". I personally really prefer the 2-line construction.

[ Parent | on HN ]