3 ms·
I wouldn’t use Java again because I am done dealing with the brokenness of Maven and Gradle. They are the opposite of “little fuss and muss.” The Go build tools
by skybrian 4y ago
I wouldn’t use Java again because I am done dealing with the brokenness of Maven and Gradle. They are the opposite of “little fuss and muss.” The Go build tools fit your analogy better.
- SureshG 4y ago> The Go build tools fit your analogy better. Go uses two build tools for any non-trivial projects. One write in go.mod and another in Make :D (see this - https://github.com/kubernetes/kubernetes/tree/master/build/root https://github.com/kubernetes/kubernetes/tree/master/build/r...)
- skybrian 4y agoI think Hugo might be a better example, as a medium-sized non-trivial project: https://github.com/gohugoio/hugo https://github.com/gohugoio/hugo There is a Docker file and some shell scripts, but you build the executable using "go install".
- chii 4y ago> dealing with the brokenness of Maven people shit on maven, but i say it's much better than many other built tooling - npm, make, or custom scripts. The only thing need getting used to is that you cannot and should not stray from the maven model - fit your project's built into the maven model, rather than try to twist maven to do your bidding.
- skybrian 4y agoMaybe I haven't built anything large enough to feel the pain, but I find npm acceptable. Go's module system seems more secure, but I had little fuss using npm to build a simple web app.
- peterashford 4y agoYou dont have to use those tools, you know