On Sunday, August 22, 2021 at 11:11:23 PM UTC-4 jlfo...@berkeley.edu wrote:
> > I've noticed that few, if any, Go programs use Makefiles. Is that because > the overhead of using make is greater than the overhead of just always > compiling and linking everything? > Go had built in build caching. So it will not have to "always compile and link everything." In addition, Go builds tend to be much, much faster than most other compiled languages. As a result, Makefiles are only useful if you have other operations to perform that are not part of the normal go tooling. > One piece of evidence for this is that the Go compiler leaves no > artifacts, like object files, so as is make wouldn't fit into the current > build method. > > Cordially, > Jon Forrest > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/449781bc-1605-4acf-b03c-dab98cf710efn%40googlegroups.com.
