How to start a Go project in 2023 • Hacker News Board

Re: How to start a Go project in 2023

#41

Post by dhagz » Tue, May 23, 2023, 6:54 PM UTC

One thing for profiling HTTP services specifically, you can attach handlers for pprof data easily [0]. I usually only mount the routes if I've set a flag for it, usually something to indicate I want to run in debug mode. This does everything "for free", i.e. it starts profiling memory and CPU and then exposes the data on routes for you to visualize in the browser.

[0]: https://pkg.go.dev/net/http/pprof

Re: How to start a Go project in 2023

#42

Post by emmelaich » Tue, May 23, 2023, 6:56 PM UTC

omneity wrote: post #21

jzelinskie wrote: post #4

Things I can't live without in a new Go project in no particular order: - https://github.com/golangci/golangci-lint - meta-linter - https://goreleaser.com - automate release workflows - https://magefile.org - build tool that can version your tools - https://godoc.org/github.com/ory/dockertest/v3 - run containers for e2e testing - https://github.com/ecordell/optgen - generate functional options - https://golang.org/x/…

Are there boilerplates that include things like this? (I’m coming from the JS/TS world)

Perhaps https://github.com/lacion/cookiecutter-golang ?

Might be a little out of date.

Re: How to start a Go project in 2023

#43

Post by arriu » Tue, May 23, 2023, 6:58 PM UTC

One thing I wish there was better support for is live debugging and stepping through code.

Re: How to start a Go project in 2023

#44

Post by kortex » Tue, May 23, 2023, 7:00 PM UTC

I see $GOPATH is no longer strictly needed, which is nice. But what's the deal with $GOROOT? I seem to always need it set but I don't know if that's just my workflow or force of habit.

Re: How to start a Go project in 2023

#45

Post by icholy » Tue, May 23, 2023, 7:06 PM UTC

0zemp2c wrote: post #39

lima wrote: post #17

How to start a new Go project: go mod init mymodule Go's default toolchain is fine, everything else is optional. Some questionable advice in the article: - Vendoring dependencies using "go mod vendor" is not a good default workflow - it bloats the repo, the checked in code is impossible to review, and is generally a pain to keep up to date. Don't, unless you really have to. - There's no point in stripping a binary or…

vendoring is a bit of project smell, but for large teams it removes the confusion of who has what version of a dependency unfortunately most teams don't schedule a periodic `go mod tidy` so you just end up with ancient deps most people never read the code of the deps they pull in, so I don't think vendoring provides any security assurances

That's not what `go mod tidy` does ...

Re: How to start a Go project in 2023

#46

Post by steveklabnik » Tue, May 23, 2023, 7:08 PM UTC

bitwize wrote: post #12

[flagged]

Please don't do this.

Re: How to start a Go project in 2023

#47

Post by typical182 » Tue, May 23, 2023, 7:12 PM UTC

jasonthorsness wrote: post #15

I see the note in the article around using -ldflags="-s -w" - is there any other useful tool for binary size analysis/reduction? I was surprised when my binary size doubled when incorporating the K8s client package to get a secret; just using the HTTP secrets API manually without referencing the client package shrank the size by many MB. It would be nice to find similar opportunities for size reduction that aren’t as…

goda[0] is excellent. You do do things like:

  # show the impact of cutting any package
  goda cut ./...:all

which prints a sorted ASCII table with stats like 'size:4.4MB loc:134171' for each package, which is an estimate the savings you'd get if you eliminated that package from your binary. That is a great way to see what is unexpectedly large compared to its value.

goda has a bunch of other capabilities around dependency analysis, and was written by long-time Go contributor Egon Elbre. The examples in the README are the best way to get started after 'go install github.com/loov/goda@latest'.

[0] https://github.com/loov/goda

Re: How to start a Go project in 2023

#48

Post by bborud » Tue, May 23, 2023, 7:17 PM UTC

shellac wrote: post #19

[flagged]

What are you comparing to and what do you think the shortfalls are? What is a "modern" language?

Re: How to start a Go project in 2023

#49

Post by revskill » Tue, May 23, 2023, 7:18 PM UTC

Working with Go is boring but productive. Go libraries are reliable, fast. It's more than enough to write good software.

Re: How to start a Go project in 2023

#50

Post by shellac » Tue, May 23, 2023, 7:21 PM UTC

kortex wrote: post #38

shellac wrote: post #19

[flagged]

What's "most modern languages"? Go is better than Python's native tooling (only Poetry and other similar 3rd party tools compare). Javascript I find unruly and fragmented. "Modern" C++ is still a nightmare. Java I haven't touched but I don't exactly hear rave reviews or angry rants about, so I expect it's middling. Rust, scala, and haskell are definitely better experiences, but they are definitely in the minority in…

> What's "most modern languages"? Go is better than Python's native tooling (only Poetry and other similar 3rd party tools compare). Javascript I find unruly and fragmented.

Exactly the scale I had in mind, thanks. When I saw 'go get ' rather than dependencies added to the equivalent of a Gemfile / cargo / pom file it had concerns.