4 ms·

You still need a Makefile if you use things like godep, or their new `go generate` stuff. They have a long way to go on tooling; however, getting to say that i

by codemac 12y ago

You still need a Makefile if you use things like godep, or their new `go generate` stuff. They have a long way to go on tooling; however, getting to say that is a luxury, due to just how "right" golang has been for systems work. Golang has been amazing to work with, and has just been stupidly productive. I miss debugging (gdb) and generic compile tools like tup, but that's about it!

kyrra 12y ago
I saw a debugger[0] posted on the go-nuts mailing list today[1]. It's fairly simple at this point, but it works. [0] https://github.com/derekparker/delve https://github.com/derekparker/delve [1] https://groups.google.com/forum/#!topic/golang-nuts/bmsFE3dQQjk https://groups.google.com/forum/#!topic/golang-nuts/bmsFE3dQ...
- dawkins 12y ago
  Thank you for mentioning it. With the last version of liteIde (refactoring, jump-to, usages, info about a anything...) the only thing that I missed was a debugger. I Hope that the project gains traction.
cespare 12y ago
You don't need a Makefile for either of those.
- codemac 12y ago
  I do if I want to encode how people who consume a pile of code either add or remove dependencies, or want to edit/recompile code that was generated. And in fact, especially at my job, it's literally what I want everyone to do in a consistent way. A convenient way to do that is ask people to type 'make'.
gaius 12y ago
I don't know why people hate on Makefiles, make is great! Does exactly what it says on the tin.
- codemac 12y ago
  I don't hate Makefiles, in fact they're quite wonderful in languages that have file based build systems (see: C). I'm just tired of the go team touting that they are unnecessary.. except that every major go project has one (or something like make.go in camlistore).
diyorgasms 12y ago
Do people prefer not using Makefiles? I ask because Makefiles are a standard part of my workflow, and while I know I can 'go build' or 'go [whatever]' I still cling to my Makefiles as a preferred tool.
- GFK_of_xmaspast 12y ago
  I'm digging into cmake, because it's the one supported by clion, and I don't think I'm going back to make.
- dilap 12y ago
  I like make, and get a kick out of possible interesting successors, like tup and redo. I forced myself to stick to "go build" when starting out with go, and I'm glad I did...more time working on what I'm working on, less time fiddling with the build system. I'd recommend it, at least until you really hit its limitations.

by codemac 12y ago

kyrra 12y ago

I saw a debugger[0] posted on the go-nuts mailing list today[1]. It's fairly simple at this point, but it works. [0] https://github.com/derekparker/delve https://github.com/derekparker/delve [1] https://groups.google.com/forum/#!topic/golang-nuts/bmsFE3dQQjk https://groups.google.com/forum/#!topic/golang-nuts/bmsFE3dQ...

dawkins 12y ago
Thank you for mentioning it. With the last version of liteIde (refactoring, jump-to, usages, info about a anything...) the only thing that I missed was a debugger. I Hope that the project gains traction.

cespare 12y ago

You don't need a Makefile for either of those.

codemac 12y ago
I do if I want to encode how people who consume a pile of code either add or remove dependencies, or want to edit/recompile code that was generated. And in fact, especially at my job, it's literally what I want everyone to do in a consistent way. A convenient way to do that is ask people to type 'make'.

gaius 12y ago

I don't know why people hate on Makefiles, make is great! Does exactly what it says on the tin.

codemac 12y ago
I don't hate Makefiles, in fact they're quite wonderful in languages that have file based build systems (see: C). I'm just tired of the go team touting that they are unnecessary.. except that every major go project has one (or something like make.go in camlistore).

diyorgasms 12y ago

Do people prefer not using Makefiles? I ask because Makefiles are a standard part of my workflow, and while I know I can 'go build' or 'go [whatever]' I still cling to my Makefiles as a preferred tool.

GFK_of_xmaspast 12y ago
I'm digging into cmake, because it's the one supported by clion, and I don't think I'm going back to make.
dilap 12y ago
I like make, and get a kick out of possible interesting successors, like tup and redo. I forced myself to stick to "go build" when starting out with go, and I'm glad I did...more time working on what I'm working on, less time fiddling with the build system. I'd recommend it, at least until you really hit its limitations.