Here's something I noticed that bugged me in the article.
It claims that Node.js wins for build process because Java's popular build processors require you to write XML.
Which makes me think they're not aware of what Apache Maven actually is.
Maven is much more than just a build tool. It not only is used to control the build order of a multi-project build, but it also downloads and installs your project's dependencies from the Maven Central repository.
You need a JSON parser in your project? Easy, just add a dependency reference with groupId com.google.code.gson and artifactId gson . Need version 2.2.1 specifically? That's alright as Maven allows you to specify a specific version.
GSON probably has its own dependencies... which Maven will also download for you.
Having said all that, if you want a build system closer to Java, you could always use the Gradle dependency manager, whose configurations are written in Groovy (a JVM language). Incidentally, you can configure Gradle to look at Maven Central for dependency resolution, too.