It feels like a big important topic for frameworks and generic code in Java land. Reading Jackson source code and seeing the reflection code is interesting.
Question is why Jackson and other libraries don't take a dependency on that? One reason could be due to the ergonomics of using it. One other reason could be due to the pain in taking on a dependency (however benign). Another reason could be the cost of switching out a working solution without a clear benefit (if there is a community consensus around reflection libraries then it would be easier). Capturing the needed knowledge that has been caught in reflection based libraries is probably not an easy thing.
It feels like a big important topic for frameworks and generic code in Java land. Reading Jackson source code and seeing the reflection code is interesting.
https://github.com/FasterXML
There is the reflection library:
https://www.baeldung.com/reflections-library
Question is why Jackson and other libraries don't take a dependency on that? One reason could be due to the ergonomics of using it. One other reason could be due to the pain in taking on a dependency (however benign). Another reason could be the cost of switching out a working solution without a clear benefit (if there is a community consensus around reflection libraries then it would be easier). Capturing the needed knowledge that has been caught in reflection based libraries is probably not an easy thing.