2 ms·
I'm sure it is highly regarded... My own (admittedly limited) experience is it is a hell hole of abstraction, vast stack traces, obscure error messages and grin
by MattPalmer1086 4y ago
I'm sure it is highly regarded... My own (admittedly limited) experience is it is a hell hole of abstraction, vast stack traces, obscure error messages and grindingly slow performance.
Apparently the things I want to do are either impossible or require so much indirection it's easier to rip it out and just write it yourself...
You may have detected I'm not a fan!
- piva00 4y agoYes, it takes time to learn a complex framework. With Spring Boot a lot has been simplified, I never used Spring before that because I had similar thoughts as you. Nowadays when I have to work without Spring (my current job doesn't use it, for example) I keep yearning for it as there's just so much productivity gains after you know the framework. It's funny because I have said in the past the exact same arguments as you, it just comes from lack of experience. I recommend stop hating it and sincerely give a try on properly learning and using it for a while, I still have some reservations and grievances with Spring but not these shallow ones :)
- MattPalmer1086 4y agoI don't really disagree with you. I'm sure it's possible to be really productive in it. It has a steep learning curve of course. Having said that, I stand by my performance criticism. I have done some detailed profiling on spring and non spring versions of code (I didn't write the spring parts, a spring expert did). It really does add a lot of overhead to start up and transactions vs. straightforward POJOs and JDBC code.
- piva00 4y agoWas this profiling done while using `JdbcTemplate`? To be honest I don't use much more than that for querying RDBMSs, I don't like any kind of ORM and actively avoid them.
- MattPalmer1086 4y agoNo, just straight JDBC, no Spring classes at all.