Hacker News Reader

Comment by vbezhenar | Hacker News Reader

I guess I'm alone in 2018 year, but I implemented new project with Spring 5 and XML configuration which works just fine and I think that it's easier to understand and support than Java configuration (or autowiring which I never use, because explicit is better than implicit even at the cost of boilerplate).

View on HN

> explicit is better than implicit

You may be interested in programmatic / functional bean registration[0], which was introduced in Spring Framework 5. It has a particular focus on Kotlin support[1][2].

[0] https://springoneplatform.io/sessions/programmatic-bean-regi...

[1] https://spring.io/blog/2017/08/01/spring-framework-5-kotlin-...

[2] http://ilities.co/2017/09/10/annotation-free-spring/

No. I completly agree with, it's far easier than debugging what configuration has been applied due to specfic annotations used.

You can use Java explicit configurations without Spring boot magic. Using XML to configure an app is so backward to me and prone to error, not to mention debugging. When I see xml config file in 2018 I want to poke my eye out.

I don't like XML either but I can clearly see the point in being explicit.

Unless you're working alone or unless everybody knows exactly how the whole system works, being explicit will save you a lot of time.

If you're still insisting, I suggest you to clone random mid-size spring project from github and do some non-trivial change (like implement automatic tracking of all changes or soft-deletes)

Reply on news.ycombinator.com