Re:History of Spring Framework and Spring Boot
by vbezhenar on Monday April 02, 2018 @12:50AM
(#16732422)
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).
[ Parent
| on HN ]
Re:History of Spring Framework and Spring Boot
by jacques_chester on Monday April 02, 2018 @07:00PM
(#16740239)
> 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-...
Re:History of Spring Framework and Spring Boot
by beepbeepbeep1 on Monday April 02, 2018 @01:45AM
(#16732582)
No. I completly agree with, it's far easier than debugging what configuration has been applied due to specfic annotations used.
Re:History of Spring Framework and Spring Boot
by ssijak on Monday April 02, 2018 @03:40AM
(#16732973)
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.
Re:History of Spring Framework and Spring Boot
by cztomsik on Monday April 02, 2018 @06:59AM
(#16733579)
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)