Java codebase, ecosystem, Maven, Spotless
Recently I have written Java code on a daily basis. After using Python and Go for years, the Java ecosystem feels complete and more enterprise-friendly.
At the same time, some parts feel verbose and outdated. Especially if you compare it to modern C# and .NET framework and what Microsoft has done for the .NET ecosystem (and open-sourcing it in general).
However, Java still has more sophisticated technologies around cross-platform native (*) desktop application development. In the web and API development era, desktop development may seem too old school. But for me, it is still a crucial part of the ecosystem.
While I am getting more and more hands-on with the Java ecosystem, I am using Spotless more and more. Keeping code style and formatting consistent across all project parts is crucial. Spotless provides a modular approach and can be configured to auto-format various file extensions.
I share some essential information about Spotless and how to configure it in the attached post.
Kanan Rahimov
(*) being "native" can mean various things depending on the context and level of abstraction. Please refer to this article, section "A small rant about native."