Hacker News Reader

What do you define as "Legacy?"

I groan every time I come across a Maven project, which AFAIK isn't quite yet "legacy."

What about dependecy management, testing, building, and all of the other non-java-code bits? Gradle only goes so far in my limited experience.

The non-Java parts of Java development are what repeatedly get me to choose Go, Ruby, Python, TypeScript/node.js, etc. The tooling is magnitudes easier to use.

Genuinely curious! Thx.

(edit: typo)

View on HN

Not who you are replying to but I would define legacy as any project that is doing spring di and wiring the project together with XML (excluding Pom for maven building), rather than annotations or raw Java code. Or anyone still deploying to an application server.

But the project configuration has nothing to do with the web framework. You can use Javalin with Maven (and therefore XML), too. And you can use Spring without any XML by configuring the project with Gradle's Kotlin DSL. Modern Java development is not what it was 20 years ago.

Reply on news.ycombinator.com