5 ms·
Gradle might not be perfect, but it's so much better than anything else I've used. Simple builds have simple config. Doing more complicated things means you
by WatchDog 6y ago
Gradle might not be perfect, but it's so much better than anything else I've used.
Simple builds have simple config.
Doing more complicated things means you need to learn how the tool works, and that can certainly take some time.
I'm really liking the new kotlin DSL, having great IDE support, really makes writing gradle scripts much more pleasant.
I do a fair bit of work on node based projects, and the building tooling in the node ecosystem is just so horrible in comparison.
- pas 6y agoNodeJS building tool? Do you mean gyp (which is bad) or high level stuff run via npm/yarn (which is meh) like gulp/webpack/ng whose config files are all horrible?
- lostcolony 6y agoI too would like clarity. Every time I end up having to do frontend stuff with gulp/webpack/etc I want to shoot myself, and that's fair. The few times I've had to compile native dealing with gyp has been a crapshoot (sometimes just work, sometimes painful; never as bad as gulp/webpack/etc). But most of the time, for Node development, I just need other node libraries, and it's pretty painless. Not as good as some others, but still -miles- better than Gradle.
- entha_saava 6y agoMaybe a bit off topic. But am I the only one who thinks "simple builds should have NO config"?
- ashtonkem 6y agoA strong argument for Cargo. Most cargo manifests are some dependencies and a bit of metadata, which I think we all can agree is reasonable enough.