> A typical old Java project depends on Gradle (or Maven, or even Ant), an outdated JDK, Eclipse, Protobuf tooling, XML tooling, custom tooling, you name it. Ne

> A typical old Java project depends on Gradle (or Maven, or even Ant), an outdated JDK, Eclipse, Protobuf tooling, XML tooling, custom tooling, you name it. Next, your project may require linting, formatting, and will be checked by some third party services. Recently, Docker and friends have joined the party, and a web based frontend requires TypeScript, a framework, Webpack, and many other libraries and tools. You say that as if it were a God-given truth that that is how things must be, or maybe even as if it were a good thing that that is how things are. Which could hardly be further from the truth. The solution isn't to cover all that shit up with yet another layer of cruft, but to get rid of most of this fricking cruft.