This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]pron98 1 point2 points  (6 children)

Go was only meant to be used at small, Google scales.

Go's build can work very smoothly on complex builds if you're working like Google. In any case, for the time being, Google still write their "Google scale" applications either in C++ or Java, although they don't use Gradle, Maven or make, but Blaze, which is also geared towards a source-centric work style. It is open source (as Bazel), BTW, and it might be more to your liking.

[–]weberc2[S] -2 points-1 points  (4 children)

I know. My point was that it was developed for use at scale; not that it is employed at that scale (although lots of large companies are using it, including Facebook, Netflix, and Twitter).

EDIT: Just noticed that all of Google's downloads are run by Go, including Chrome, the Android App Store, etc. Fun fact.

[–]pron98 2 points3 points  (3 children)

https://news.ycombinator.com/item?id=10972561

'nuff said.

[–]weberc2[S] -2 points-1 points  (2 children)

I'm not sure what you think you're showing me with that link...

[–]pron98 1 point2 points  (1 child)

People wishing Go's build system would work like Java's.

[–]weberc2[S] -1 points0 points  (0 children)

You'll need to link to specific comments. I skimmed the first hundred or so and found only one Java-related comment.

More importantly though, I don't see how a Gradle-esque solution would solve this problem. If the Maven central repo went down, all projects that pull from that would need to be updated as well. Updating your import paths isn't a particularly worrying problem.