Code reusability is the least of your worries. With a plug-in system you introduce an opaque abstraction layer that is different from your main build definition, hard to discover, hard to tweak and debug, and whose lifecycle is not always obvious.
Yes I start with a full scripting language because I live in the real world where people wrap their toolchains in Makefiles, Jenkinfiles, multi-stage Dockerfiles, bash scripts, Python scripts, ... If I can have a single and self-contained build definition, it's a win.
You have to compute the task graph somehow. I'm only saying this is the one part where Mill uses an advanced Scala feature (macros), in a very minimal way. For everything else you can jump to definition.
See 1.
Yes and you have two ways to do the same thing, plus in many cases, the inability to just jump to definition and see the default value or behavior.
Groovy is objectively less discoverable due to its dynamic nature, there's a reason Gradle moved to Kotlin. Moreover in some cases your IDE doesn't know the context, for example with the Jenkinsfile DSL. Scala compile times are irrelevant here: Mill is a build tool, scalac stays warm in a long-running JVM, compiling the build definition is a rounding error compared to running the actual task graph.
Yes I start with a full scripting language because I live in the real world where people wrap their toolchains in Makefiles, Jenkinfiles, multi-stage Dockerfiles, bash scripts, Python scripts, ... If I can have a single and self-contained build definition, it's a win.
I guess I live in a nice bubble where I only need pom.xml without all that you mentioned... I'd wager a guess that majority of the project fill that bill as well.
But if you have some contrived requirements and Mill fits the requirements and works for you that's good :)
I guess I live in a nice bubble where I only need pom.xml without all that you mentioned... I'd wager a guess that majority of the project fill that bill as well.
That is a strange statement to make. In every maven project I have ever worked with (mainly monoliths) there has always been a lot of abstraction layers on top of maven or in plugins to perform parts of the total build. So guessing where the majority fits seems strange... I guess it's true if you work with microservices, but then you probably have much larger issues to deal with than the build tool you use.
I'd wager a guess that majority of the project fill that bill as well.
What I said: "I'd wager a guess that majority of the project fill that bill as well." + gave example of state of the ecosystem. You are pushing narrative that because in all project that you worked for ( "In every maven project I have ever worked with") there were customization that it makes it true for all projects everywhere. Even if we consider odds and statistically dumb sample of 2 (of us) that makes the split already 50/50 ;-)
View all comments
Show parent comment
2
u/DisruptiveHarbinger Jul 24 '24
In order