4 ms·
I believe you're right, though I think it's Spring's inversion of control rather than the annotations themselves. The problem with inversion of control is that
by jfengel 6y ago
I believe you're right, though I think it's Spring's inversion of control rather than the annotations themselves.
The problem with inversion of control is that if you get it wrong, there is no feedback. All you get is "nothing happened". When it works, it just works, which is great. When it doesn't work, it doesn't work, and "it doesn't work" is practically impossible to Google. Spring had the same problems, worse, with XML configuration.
The solution is exactly as you say: let programmers program. Solve the problem with debugging tools that you already know, rather than introducing a whole new meta-meta-programming environment without any debugging support. (If you attach a Java debugger to a running Spring program to step through the point where it's failing to find your annotation, you will regret it.)