3 ms·

I can identify myself as a strictly Java developer (nowadays) and my experience with Spring can be summarized as either: > I imported that autoconfiguration li

I can identify myself as a strictly Java developer (nowadays) and my experience with Spring can be summarized as either: > I imported that autoconfiguration library and everything works! > Damn it, the imported autoconfiguration library does not work (or I need to change something), now I have to spend a day around Spring docs and stackoverflow to find how to get it working. Than I have to create a new class, override some random methods and inject my ugly code which feels like a hack now...

krooj 7y ago
This hits home. A lot of my work seems to be mopping up the mess that developers created by doing the former and applying the latter. Autoconfiguration is great for quick demo-days and a literal cancer for everything else. Frankly, after some recent development on ES6 + node + express, I'm starting to question whether staying on Spring + Java is worth it.
oauea 7y ago
Just read the source. You can jump to the implementation of the autoconfiguration in your IDE, and they're usually only a dozen lines or so of bean creation.