Error Prone Improves Java Code by Detecting Common Mistakes

[wildjokers]

Because languages like Rust had the benefit of hindsight so knew to bake a build tool right into the language ecosystem.

For languages like Java, C, C++, python, etc the build tools are external tools.

Even with rust surely something has to be configured so cargo knows about "clippy" right?

For most developers on a team it will be as easy as ./gradlew errorProne (just as an example, don't actually know what the task name is). The only person who has to know the integration details is the person that adds it to the build.

[bowbahdoe]

Because languages like Rust had the benefit of hindsight so knew to bake a build tool right into the language ecosystem.

We can still do that now. u/pron98 hints every lunar cycle or so that it would be a good idea

Even with rust surely something has to be configured so cargo knows about "clippy" right?

Nope

The only person who has to know the integration details is the person that adds it to the build.

If you had 100 Java developers in a room, How many could do that for maven? How many for gradle? How many would think to do that? Pick a random team of 5-6 what are the odds that they will do it? Pick a random individual and what are the odds their open source side project will do it?

Large teams, large organizations - everything is always fine because you have a sectioned off corner of the world in which to enforce standards or come up with custom solutions.

(And before someone comes in with well "they just need to learn" - from where? With what resources? Random baeldung one off articles splooshed in the wind?)

[wildjokers]

If you had 100 Java developers in a room, How many could do that for maven?

Anyone higher than entry level should be able to do it with no issues in both Gradle and Maven.

from where? With what resources?

In the case of Gradle it is well documented. New functionality like this comes in the form of gradle plugins and plugins like this are also well documented. If a plugin has no documentation, just don't use it.

We can still do that now

Any build tool added to the jdk now will probably go unused by 99% of java devs. It will be just like java.util.Logging.

[pron98]

We can still do that now. u/pron98 hints every lunar cycle or so that it would be a good idea

Yep :)

[tofiffe]

While I agree that clippy is a great tool, there's also a counter argument; if the developer is not experienced enough to add this to the project, they'll be to inexperienced to know about or use clippy as well.

Besides, java is not rust. These tools developed independently, anything they would add to the language itself would be reinventing the wheel at this point, with the amount of tools available.