3 ms·
> (gradle, I'm looking at you!) gradle has pretty much the worst ergonomics of any developer tool I've ever used[1], so that's a pretty low bar. [1] e.g. "Som
by js2 5y ago
> (gradle, I'm looking at you!)
gradle has pretty much the worst ergonomics of any developer tool I've ever used[1], so that's a pretty low bar.
[1] e.g. "Something went wrong. Re-run with -debug or -info. Now here's 5000 lines of useless stack traces that won't help at all." Nevermind an ecosystem of plugins where it's not clear where the DSL ends and API starts, and makes it virtually impossible to locate the actual source of an error message, if you get one at all.
- mumblemumble 5y agoThis time last year, I was deep into writing Gradle plugins at work. Gradle's entire architecture is the best argument I have ever seen for why you should never use a big blob of shared mutable state when all you really needed to do was pass discrete values up and down the call stack. Compare with Bazel. I appreciate why people bounce off of many of its strictures. But when you just look at the architecture and what it takes to develop for it, it's amazing how much easier it is to grok, while achieving a similar level of flexibility.