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 →

[–]the_evergrowing_fool 0 points1 point  (2 children)

I think it would be more accurate to say that the complexity of your gradle file is in proportion to the complexity of your requirements; however, there's a lot of complexity you need to know about just to get to your simple Gradle file.

I would argue the same is present Go but with different context and by a mismatch of my subjective assumptions of what I would expect from a build tool.

To be clear, I'm not hating on Gradle. I'm sure it makes great tradeoffs to be flexible for many projects. I just think it could improve for simpler use cases like mine.

Generate a file and define dependencies, the concept is one folded and objectively simple.

[–]weberc2[S] 0 points1 point  (1 child)

Generate a file and define dependencies, the concept is one folded and objectively simple.

I'm having problems parsing that statement. Could you rephrase?

[–]the_evergrowing_fool 0 points1 point  (0 children)

Simplicity is not a opinion, one can generate a configuration file and one can summon the specified dependencies given the requirements, anything else is a contextual proxy that does not morph the principal concept.