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

Practical Go: Real-world advice for writing maintainable Go programs

dave.cheney.net

Post reply on HN
Print view View original

11–20 of 237 posts

Re: Practical Go: Real-world advice for writing maintainable Go programs

#11

Post by amedvednikov »

axaxs wrote: post #6
amedvednikov wrote: post #3

Great article, as always, by Dave Cheney. I took a lot of his advice when designing V [1]. It's very similar to Go, but it has - No global state - Only one declaration style (a := 0) - No null - No undefined values - No err != nil checks (replaced by option types) - Immutability by default - Much stricter vfmt - No runtime - Cheaper interfaces without dynamic dispatch [1] http://vlang.io

Just wanted to say...as both a language nerd and opinionated snob, I'm really excited by what I see with V thus far. I'll be following your progress for sure and wish you the best.

Thanks!

Re: Practical Go: Real-world advice for writing maintainable Go programs

#12

Post by stouset »

amedvednikov wrote: post #3

Great article, as always, by Dave Cheney. I took a lot of his advice when designing V [1]. It's very similar to Go, but it has - No global state - Only one declaration style (a := 0) - No null - No undefined values - No err != nil checks (replaced by option types) - Immutability by default - Much stricter vfmt - No runtime - Cheaper interfaces without dynamic dispatch [1] http://vlang.io

This seems to address basically all of my frustrations with go. Well done!

Re: Practical Go: Real-world advice for writing maintainable Go programs

#13

Post by dilap »

letientai299 wrote: post #5

Came from Java world, I find the Go comment and godoc are really limited. We can't link between functions, types. We don't have a standard way to declare input, output, don't have any distinction between a normal word and a Go identifier Refactoring using tool (e.g: Goland) usually lead to unexpected text replacements. Take following functions, for example: // Auth check if user credential is existed in bla, bla... /…

Flip-side is less complexity and the doc comments in raw code look better. Go's generally all about, "how much can we strip away and still have things work".

Your criticisms re refactorings and links are on point though.

Trade-offs.

Re: Practical Go: Real-world advice for writing maintainable Go programs

#15

Post by SaulOfTheJungle »

amedvednikov wrote: post #3

Great article, as always, by Dave Cheney. I took a lot of his advice when designing V [1]. It's very similar to Go, but it has - No global state - Only one declaration style (a := 0) - No null - No undefined values - No err != nil checks (replaced by option types) - Immutability by default - Much stricter vfmt - No runtime - Cheaper interfaces without dynamic dispatch [1] http://vlang.io

> - No err != nil checks (replaced by option types)

Where can I find code illustrating V Option types?

Re: Practical Go: Real-world advice for writing maintainable Go programs

#16

Post by arendtio »

> A good Go package should strive to have a low degree of source level coupling such that, as the project grows, changes to one package do not cascade across the code-base.

I wonder though why there is so little emphasis on how important interfaces are in Go. I mean, section 4.5 talks about it a bit, but in my experience, this mistake is made far too often.

Re: Practical Go: Real-world advice for writing maintainable Go programs

#17

Post by amedvednikov »

SaulOfTheJungle wrote: post #15
amedvednikov wrote: post #3

Great article, as always, by Dave Cheney. I took a lot of his advice when designing V [1]. It's very similar to Go, but it has - No global state - Only one declaration style (a := 0) - No null - No undefined values - No err != nil checks (replaced by option types) - Immutability by default - Much stricter vfmt - No runtime - Cheaper interfaces without dynamic dispatch [1] http://vlang.io

> - No err != nil checks (replaced by option types) Where can I find code illustrating V Option types?

https://github.com/vlang-io/V/blob/master/examples/users.v

They are very simple and combine Rust's Option and Result.

Re: Practical Go: Real-world advice for writing maintainable Go programs

#18

Post by jstewartmobile »

Love Mr. Cheney, hate stuff like this.

Someone who has put the hours in will probably stray from all of this advice, and still end up with something beautiful. Meanwhile, for all of the other schmoes who haven't put the hours in, this is just more fuel for screeching about how this name isn't right or that comment is too long.

Dijkstra said GOTO was bad, and now we have callback hell and 10-layer inheritance hierarchies instead.

Re: Practical Go: Real-world advice for writing maintainable Go programs

#19

Post by jstewartmobile »

letientai299 wrote: post #5

Came from Java world, I find the Go comment and godoc are really limited. We can't link between functions, types. We don't have a standard way to declare input, output, don't have any distinction between a normal word and a Go identifier Refactoring using tool (e.g: Goland) usually lead to unexpected text replacements. Take following functions, for example: // Auth check if user credential is existed in bla, bla... /…

I guess it's hard to get around to the advanced features when so few people even bother to take advantage of the basic ones.

Documentation for most Go libraries I've come across has been pathetic compared to similar things in Python or PHP.

edit: Compare to something like Racket: https://docs.racket-lang.org/plot/intro.html?q=graph#%28part...

Re: Practical Go: Real-world advice for writing maintainable Go programs

#20

Post by wuschel »

amedvednikov wrote: post #3

Great article, as always, by Dave Cheney. I took a lot of his advice when designing V [1]. It's very similar to Go, but it has - No global state - Only one declaration style (a := 0) - No null - No undefined values - No err != nil checks (replaced by option types) - Immutability by default - Much stricter vfmt - No runtime - Cheaper interfaces without dynamic dispatch [1] http://vlang.io

Exciting!

How long was this language in development? In what language was the compiler originally written in?

Post reply on HN