personally I prefer not to add another dependency ...

# spring

[roberto.guerra]

personally I prefer not to add another dependency and just use the open keyword. Even with Spring Boot, I keep most (if not all) business logic outside of Spring, and just use a thin layer of spring artefacts to wire them up. So adding open isn’t a hassle for me. I can see how it is a hassle if most things in the application are some sort of spring “artefact”.

[suresh]

roberto.guerra: IIUC, these are (all-open, kotlin-spring) kotlin compiler gradle plugins. So no runtime overhead or extra dependency in jar.

[roberto.guerra]

Yes, I understand, but I still don’t like adding more to the gradle file than what is needed. Also, when I stumble on issues like this, I like to step back and think. And what Kotlin ‘final by default’ taught me was that I was putting too much logic inside Spring artefacts, which smelled to me. I like being pinched when something about my code is wrong. 🙂