3 ms·
Spring proper is (relatively) fine; you can make applications with it that are more-or-less maintainable. Spring Boot is very different. It's a write-only frame
by lmm 6y ago
Spring proper is (relatively) fine; you can make applications with it that are more-or-less maintainable. Spring Boot is very different. It's a write-only framework, and while businesses may have enthusiastically adopted it, it's new enough that they haven't (yet) had to pay the maintenance costs and realise how bad they are.
- simmerup 6y agoWhat do you mean by write-only framework?
- nwatson 6y agoWOF == you understand your software while you're writing/developing it but give it a rest for a Trump's "two weeks" and you'll have no clue what you did.
- Pet_Ant 6y agoApparently Donald Trump always said "two weeks". I was unaware of this meme. * https://www.axios.com/trumps-timeline-always-two-weeks-1513302785-b6370a4f-bb5e-434a-80ca-1249c7cf2baa.html https://www.axios.com/trumps-timeline-always-two-weeks-15133... * https://www.bloomberg.com/news/articles/2017-06-06/in-trump-s-white-house-everything-s-coming-in-two-weeks https://www.bloomberg.com/news/articles/2017-06-06/in-trump-...
- evilduck 6y agoWrite-only in this context means that the cost of maintaining something vastly exceeds the cost of rewriting that something from scratch. I don't know Spring and Spring Boot well enough to pass judgement, but this situation generally arises in software when you have a language or framework that's reasonably expressive, where the language has a lot of sigils or keywords and it has "shortcuts" that you have to grok before you can really understand codebases that use those shortcuts (like annotations or heavy/excessive use of design patterns). It leads to software solutions that are only well understood by the original authors due to their specific knowledge and problem solving approach and anyone who comes along later must have the exact same overlap of knowledge and skills otherwise they'll find it easier to start fresh. This includes the original authors if the time lapse has been long enough. This often then leads to the next phase of miserable software jobs, the second-system effect.
- krooj 6y agoI agree with this, having recently gone through the exercise of creating some "onboarding" apps for new grads using Spring 5 and XML, then again with annotations. All the underpinnings for a non-Boot application are still there and mainly sane. Spring Boot absolutely yields write-once throw away, and you _must_ consider the source: Pivotal is a contracting shop, so it's in their interests to hook people into an ecosystem that they happen to be experts in. I'm surprised this fact is lost on most.