4 ms·
I'm not critical of spring because real life software projects are messy. I'm critical because I rarely if ever do greenfield development and when I'm debugging
by zaphar 6y ago
I'm not critical of spring because real life software projects are messy. I'm critical because I rarely if ever do greenfield development and when I'm debugging a production exception caused by something that Java's type system was perfectly capable of treating as a compile time error that is suddenly a runtime error I'm a little bit sad. And the sheer frequency that I encounter them indicates that just getting more disciplined developers isn't really a solution here.
- selfhoster11 6y agoThe real solution is to bite the bullet and build Spring's features into Java. Make as many failures as possible detectable during compilation, and go back to hard typing.
- diroussel 6y agoMicronaut gives you that. Compile time validation of your bean wiring.
- throwaway4good 6y agoOr maybe if you just want to hardwire your dependencies, you shouldn't use dependency injection.
- blandflakes 6y agoI guess at the end of the day I just don't feel like I need Spring's features.
- thomascgalvin 6y agoThe number of time's I've seen an error that amounts to `this instance of Foo should have been a FooBar, not a FooBatz` is really depressing.