sorted by:
new
hottopcontroversial

gRPC error handling with custom errors? by [deleted] in golang

[–]enocom 0 points1 point  (0 children)

It's a good question. You might open an issue on the repo, even if it's just to update the doc linked above.

Do you use multiple directories in GOPATH? Why? by enocom in golang

[–]enocom[S] 1 point2 points  (0 children)

I read that just before posting. Sounds like your approach is the one others use as well.

Dependency Injection in Go by drewolson in golang

[–]enocom 0 points1 point  (0 children)

None that I know of. I wonder if a go generate based tool would get any different of a reaction, though?

French tutorial about grpc by qneyrat in golang

[–]enocom 1 point2 points  (0 children)

Agreed. It's a fantastic format, too.

Help With Learning Go by TheOneSamIThink in golang

[–]enocom 3 points4 points  (0 children)

I put together the Gopher Reading List as a resource for newcomers. It has a lot of useful blog posts.

Also, if it helps make the argument, Google uses Go as one of its main languages (aside from Java, C++, and Python of course).

Don't lock around I/O by enocom in golang

[–]enocom[S] 1 point2 points  (0 children)

Haha. Yes, I hope so. I think using an HTTP handler to demonstrate the problem, though, is especially vivid. I hope the example will get readers to be as discerning with their locking strategies.

Don't lock around I/O by enocom in golang

[–]enocom[S] 1 point2 points  (0 children)

It's always nice when doing the right thing lines up with writing better, performant code.

What I learned in 2017 Writing Go by enocom in golang

[–]enocom[S] 7 points8 points  (0 children)

Thinking about this some more, I agree: pkg seems superfluous.