Re:Java 12
by ivan_gammel on Wednesday March 20, 2019 @03:09PM
(#19445702)
Newbie can write bad code on any platform, but it‘s a short period of life of software developer - the problem of beginners is solved not by the tools they use, but through a reasonable composition of the team with sufficient number of experienced developers who can define the architecture and best practices.
From what I can tell, the "bad" Spring code is the code following the recommended Best Practices, at least according to the tutorials that pop up in Google search results.
Re:Java 12
by ivan_gammel on Thursday March 21, 2019 @02:43AM
(#19449685)
There’s one “must read” tutorial - documentation on official Spring website. There’s also github account with lots of examples. It’s better to ignore the trash that comes from search results, because either it’s trivial or obsolete.
Another related surprising thing (as I'm currently learning Spring/Hibernate/etc.) is what happens when the Hibernate Validator library is missing at runtime:
Nothing.
All the carefully crafted validation annotations just don't do anything, no validation is performed, and there is no indication whatsoever of this.
Re:Java 12
by ivan_gammel on Thursday March 21, 2019 @02:37AM
(#19449669)
It’s not a problem with annotations or Spring - could happen e.g. with SPI and anything that’s discovered in runtime. It’s about how you build your project and configure dependencies (separation of API and implementation in different JARs is typical for Java and implies certain way of thought about build and deployment).
It's not that Spring is badly coded or something, I just don't need these surprises and the magical thinking surrounding newbie Spring Boot projects.