The article is pretty interesting but it would have been nice to see some code examples
You said that frameworks often are context eaters, and Spring is one of them so you are discouraging to rely too much on it, did I get it wrong? But then how do you properly handle dependencies without too much boiler plate code?
As for Spring. There are many other DI containers out there, Spring is definitely not the best of them (I'd say worst, but this is mostly irrelevant). Some DI containers, for example, Guice, use explicit configuration and this preserves much more context than Spring does. Haven't tried Micronaut, but givent that it uses compile-time annotation processing, it should address at least some Spring pain points.
The article is pretty interesting but it would have been nice to see some code examples
You said that frameworks often are context eaters, and Spring is one of them so you are discouraging to rely too much on it, did I get it wrong? But then how do you properly handle dependencies without too much boiler plate code?
Some code examples are provided in the Introduction To Pragmatic Functional Java article and several others from my blog: here and here. Finally, there is a (WIP) demo project at GitHub.
As for Spring. There are many other DI containers out there, Spring is definitely not the best of them (I'd say worst, but this is mostly irrelevant). Some DI containers, for example, Guice, use explicit configuration and this preserves much more context than Spring does. Haven't tried Micronaut, but givent that it uses compile-time annotation processing, it should address at least some Spring pain points.
Thank you very much @siy