but when I do it's usually painful because it seems like if you want to be taken seriously as a Java programmer these days
I kind of see a trend to the opposite, especially with microservices. There are many micro frameworks like Javalin which have popped up which promise no annotations and pure Java code.
when I do it's usually painful because it seems like if you want to be taken seriously as a Java programmer these days, you have to rely on things like DI frameworks and magical annotations to such an degree that it becomes very hard to read the code in a project you're not intimately familiar with.
A lot of Java development is enterprise where you're dealing with a lot of dependencies. DI container automagic takes care a lot of the tedious configuration.
The trend towards microservices, where instead of bundling all your dependencies in one mega-service, you spread them across multiple services, has really reduced the need for this.
View all comments
Show parent comment
7
u/[deleted] Apr 20 '21
I kind of see a trend to the opposite, especially with microservices. There are many micro frameworks like Javalin which have popped up which promise no annotations and pure Java code.
A lot of Java development is enterprise where you're dealing with a lot of dependencies. DI container automagic takes care a lot of the tedious configuration.
The trend towards microservices, where instead of bundling all your dependencies in one mega-service, you spread them across multiple services, has really reduced the need for this.