I love this in concept, but I fear the build tool space is so much like herding cats that I'm not sure I have high hopes on anything that tries for solid standardization.
It is hard.
On the other hand solutions like Bazel (developed and used by Google) and Buck (Facebook) get pretty close to it.
I mean, they are not interchangeable but once you have picked one you can use them to build basically any language.
I think, at the scale of those companies, you cannot really let each team decide if they are going to use Maven, Gradle or Ant for Java because that would cause an explosion of different build strategies.
So main reason for using them is reduction of cognitive burden, but also the technical one, since it is not always simple to integrate a package build with X with another package build with Y.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I love this in concept, but I fear the build tool space is so much like herding cats that I'm not sure I have high hopes on anything that tries for solid standardization.
Or am I being too cynical here?
It is hard.
On the other hand solutions like Bazel (developed and used by Google) and Buck (Facebook) get pretty close to it.
I mean, they are not interchangeable but once you have picked one you can use them to build basically any language.
I think, at the scale of those companies, you cannot really let each team decide if they are going to use Maven, Gradle or Ant for Java because that would cause an explosion of different build strategies.
So main reason for using them is reduction of cognitive burden, but also the technical one, since it is not always simple to integrate a package build with X with another package build with Y.